Triple
T850226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cadet Sergeant |
E18367
|
entity |
| Predicate | hasSeniorityOver |
P12947
|
FINISHED |
| Object | junior cadet NCOs |
—
|
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: junior cadet NCOs | Statement: [Cadet Sergeant, hasSeniorityOver, junior cadet NCOs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeniorityOver Context triple: [Cadet Sergeant, hasSeniorityOver, junior cadet NCOs]
-
A.
isSeniorTo
chosen
Indicates that one entity holds a higher rank, status, or level of authority than another.
-
B.
hasSeniorNCO
Indicates that an entity has, is assigned, or is associated with a senior non-commissioned officer in a supervisory or leadership capacity.
-
C.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
-
D.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
-
E.
leaderSince
Indicates that an entity has held a leadership role over another entity starting from a specified point in time.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac215194819099e6bc1b5df58fb3 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa81ef348190b067f817574e9efe |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.