Triple
T14470047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Elephant |
E358814
|
entity |
| Predicate | mentionsArmy |
P114774
|
FINISHED |
| Object | army accompanied by elephants |
—
|
LITERAL 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: army accompanied by elephants | Statement: [The Elephant, mentionsArmy, army accompanied by elephants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionsArmy Context triple: [The Elephant, mentionsArmy, army accompanied by elephants]
-
A.
countryMilitary
Indicates that a country possesses, controls, or is associated with a particular military force or armed organization.
-
B.
militaryIssue
Indicates that one entity formally provides or distributes military-related items, orders, or directives to another entity.
-
C.
groundForces
Indicates that one entity deploys, commands, or involves military forces operating on land in relation to another entity or context.
-
D.
armedForcesInvolved
Indicates that the relationship or event involves the participation or presence of military or armed forces.
-
E.
hasMilitaryAssociation
Indicates a relationship in which an entity is connected or affiliated with a military organization, activity, or function.
- F. None of above. chosen
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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91f969788190a5114f92d7159aae |
completed | April 14, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de610330a48190b558235a14c0dc9f |
completed | April 14, 2026, 3:45 p.m. |
Created at: April 10, 2026, 1:20 a.m.