Triple
T7910085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parker Selfridge |
E183673
|
entity |
| Predicate | ordersOrApproves |
P37325
|
FINISHED |
| Object | military action against the Na'vi |
—
|
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: military action against the Na'vi | Statement: [Parker Selfridge, ordersOrApproves, military action against the Na'vi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordersOrApproves Context triple: [Parker Selfridge, ordersOrApproves, military action against the Na'vi]
-
A.
orderAuthority
chosen
Indicates that one entity has the formal power or right to issue orders or directives to another entity.
-
B.
ordersBy
Indicates that one entity arranges, sorts, or sequences another entity according to a specified criterion or set of criteria.
-
C.
order
Indicates that one entity requests, arranges, or directs that another entity provide a good, service, or action, typically in a specified sequence or priority.
-
D.
orderClass
Indicates that one entity is classified into a particular order or category within a hierarchical or taxonomic system.
-
E.
orderGroup
Indicates that multiple individual orders are associated together as a single grouped order entity or batch.
- F. None of above.
Provenance (3 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a5db9508190bbe92673ef5a7861 |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:04 p.m.