Triple
T36164360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Theodore Roosevelt |
E1045957
|
entity |
| Predicate | RCOHPeriod |
P184983
|
FINISHED |
| Object | 2009–2013 |
—
|
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: 2009–2013 | Statement: [USS Theodore Roosevelt, RCOHPeriod, 2009–2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RCOHPeriod Context triple: [USS Theodore Roosevelt, RCOHPeriod, 2009–2013]
-
A.
periodReception
Indicates a temporal relationship where one entity receives, hosts, or is associated with another during a specific time period or interval.
-
B.
reorganizationPeriod
Indicates the time span during which a structural or organizational change is planned, underway, or in effect.
-
C.
administrationPeriod
Indicates the time span during which an entity is responsible for administering, managing, or governing another entity or resource.
-
D.
revisionPeriod
Indicates the time span or interval during which a revision or update to something is in effect or expected to occur.
-
E.
capturesPeriod
Indicates that one entity records, encompasses, or represents a specific span of time associated with another entity.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b69a74a08190b31b1201278a2c57 |
completed | May 3, 2026, 8:56 p.m. |
Created at: May 3, 2026, 4:08 p.m.