Triple
T23489767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Short Service Commission |
E570636
|
entity |
| Predicate | initialTenure |
P152575
|
FINISHED |
| Object | typically 10 years in many branches |
—
|
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: typically 10 years in many branches | Statement: [Short Service Commission, initialTenure, typically 10 years in many branches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialTenure Context triple: [Short Service Commission, initialTenure, typically 10 years in many branches]
-
A.
laterTenure
Indicates that one entity’s tenure or term of service occurs after another entity’s tenure or term of service.
-
B.
lifeTenure
Indicates that an individual holds a position or office for the duration of their lifetime, without a fixed term limit or routine reappointment.
-
C.
tenureType
Indicates the type or category of tenure or contractual engagement that characterizes the relationship between the involved entities.
-
D.
teamTenure
Indicates the duration or length of time an entity has been part of a particular team.
-
E.
isTenuredPosition
Indicates that a position is a permanent academic or professional role typically protected from arbitrary dismissal.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7dba7388190a322ab059bb6522a |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 6:04 p.m.