Triple
T9595252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander of the Air Force (Sri Lanka) |
E231514
|
entity |
| Predicate | rankHeld |
P7155
|
FINISHED |
| Object | Air Marshal |
—
|
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: Air Marshal | Statement: [Commander of the Air Force (Sri Lanka), rankHeld, Air Marshal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankHeld Context triple: [Commander of the Air Force (Sri Lanka), rankHeld, Air Marshal]
-
A.
rankHeldByPost
chosen
Indicates that a particular organizational post or position is associated with, or carries, a specific rank.
-
B.
typicallyHoldsRank
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
-
C.
rankHeldByOfficeholder
Indicates the specific rank or level associated with an office or position that is held by a particular officeholder.
-
D.
rankStatus
Indicates the hierarchical level or position an entity holds within an ordered ranking or status system.
-
E.
positionHeld
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
- 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a14fd308190beb8fda5a9e912c7 |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:07 p.m.