Triple
T16804219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Langley |
E408436
|
entity |
| Predicate | reclassifiedDate |
P124704
|
FINISHED |
| Object | 1937-04-21 |
—
|
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: 1937-04-21 | Statement: [USS Langley, reclassifiedDate, 1937-04-21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reclassifiedDate Context triple: [USS Langley, reclassifiedDate, 1937-04-21]
-
A.
reclassificationYear
Indicates the year in which something was reassigned to a different category, status, or classification.
-
B.
reclassifiedBy
Indicates that an entity’s classification or category has been changed by a specific agent or authority.
-
C.
reclassifiedAs
Indicates that an entity’s classification or category has been changed from a previous one to a new one.
-
D.
redenominationDate
Indicates the date on which a currency or financial instrument undergoes a formal change in its nominal value or unit (redenomination).
-
E.
retrocessionDate
Indicates the date on which rights, obligations, or control previously transferred are formally returned or reassigned back to the original party or another designated party.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2cb68508190a05749bad68f7b43 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e319d0fdb8819088425bd82431640f |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326bac94481908c082117553320f8 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:22 a.m.