Triple
T828427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cadet Lance Corporal |
E17908
|
entity |
| Predicate | seniority |
P12947
|
FINISHED |
| Object | junior |
—
|
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 | Statement: [Cadet Lance Corporal, seniority, junior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seniority Context triple: [Cadet Lance Corporal, seniority, junior]
-
A.
lifeTenure
Indicates that an individual holds a position or office for the duration of their lifetime, without a fixed term limit or routine reappointment.
-
B.
isSeniorTo
chosen
Indicates that one entity holds a higher rank, status, or level of authority than another.
-
C.
hasSeniorNCO
Indicates that an entity has, is assigned, or is associated with a senior non-commissioned officer in a supervisory or leadership capacity.
-
D.
designationLevel
Indicates the specific rank, tier, or level assigned to an entity within a designation or classification system.
-
E.
maturity
Indicates that an entity has reached a specified stage of development, completeness, or readiness, often marking the point at which certain rights, obligations, or behaviors become applicable.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab99b1e48190afad1f073348b29a |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa79a6488190a634388e071ed9b7 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.