Triple
T33931783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RS 1 Colin Archer |
E869915
|
entity |
| Predicate | numberOfYearsInService |
P14042
|
FINISHED |
| Object | 40 |
—
|
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: 40 | Statement: [RS 1 Colin Archer, numberOfYearsInService, 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfYearsInService Context triple: [RS 1 Colin Archer, numberOfYearsInService, 40]
-
A.
serviceNumberOrYearsOfService
Indicates a relationship that specifies either an entity’s service identification number or the duration of time the entity has served.
-
B.
hasTimePeriodOfService
Indicates that an entity is associated with a specific span of time during which it provided service or was actively serving.
-
C.
yearsOfMilitaryService
Indicates the number of years an entity has served or is recorded as serving in the military.
-
D.
serviceYears
chosen
Indicates the number of years an entity has provided service or been in a particular role, position, or organization.
-
E.
servesYears
Indicates the duration, measured in years, that an entity performs a particular role, service, or function.
- 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a036c1282748190a820562bcd9aa5d9 |
completed | May 12, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_6a036bb5ca0c8190bd50abc197960b41 |
completed | May 12, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:49 a.m.