Triple
T28715268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. claimed victory |
E729942
|
entity |
| Predicate | associatedWithForce |
P52163
|
FINISHED |
| Object | U.S. Army |
E349
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: U.S. Army | Statement: [U.S. claimed victory, associatedWithForce, U.S. Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithForce Context triple: [U.S. claimed victory, associatedWithForce, U.S. Army]
-
A.
associatedForce
chosen
Indicates that there is a force linked or connected to an entity, typically representing the physical influence acting on or exerted by that entity.
-
B.
inForceWith
Indicates that a rule, condition, or agreement is currently active and being applied in conjunction with a specified entity or set of entities.
-
C.
associatedWithAction
Indicates a general relationship where an entity is linked or connected to a particular action, without specifying the nature or direction of that involvement.
-
D.
associatedWithFront
Indicates a relationship where one entity is linked or connected specifically to the front part, side, or face of another entity.
-
E.
associatedWithMatch
Indicates a relationship where an entity is linked or connected to a particular match or matching event.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a01bcd39760819081807a02eb1939d1 |
completed | May 11, 2026, 11:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24a24ce9008190a4bada87fd8221d5 |
completed | June 6, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_6a01bc3f1c74819087580e3134affc60 |
completed | May 11, 2026, 11:23 a.m. |
Created at: April 28, 2026, 5:50 a.m.