Triple
T13233103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles W. Morgan |
E315071
|
entity |
| Predicate | yearsInService |
P106252
|
FINISHED |
| Object | about 80 years |
—
|
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: about 80 years | Statement: [Charles W. Morgan, yearsInService, about 80 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearsInService Context triple: [Charles W. Morgan, yearsInService, about 80 years]
-
A.
serviceNumberOrYearsOfService
chosen
Indicates a relationship that specifies either an entity’s service identification number or the duration of time the entity has served.
-
B.
yearsOfMilitaryService
Indicates the number of years an entity has served or is recorded as serving in the military.
-
C.
hasTimePeriodOfService
Indicates that an entity is associated with a specific span of time during which it provided service or was actively serving.
-
D.
militaryServicePeriod
Indicates the span of time during which an entity serves or has served in a military capacity.
-
E.
yearsInReserve
Indicates the number of years an entity has been held or maintained in reserve before being used, deployed, or activated.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d34ff288190bdb550a019b7a470 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:22 p.m.