Triple
T801674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transportation Security Administration |
E17140
|
entity |
| Predicate | dateMovedToParentAgency |
P18852
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Transportation Security Administration, dateMovedToParentAgency, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateMovedToParentAgency Context triple: [Transportation Security Administration, dateMovedToParentAgency, 2003]
-
A.
headquartersMovedOn
Indicates that the location of an entity’s headquarters changed on a specific date or point in time.
-
B.
formerParentOrganization
Indicates that one organization previously served as the parent organization of another, but no longer holds that status.
-
C.
removedFromJurisdictionOf
Indicates that authority, control, or legal oversight over an entity has been taken away from a particular jurisdiction.
-
D.
relocatedTo
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
E.
relocatedFrom
Indicates that an entity has moved or been transferred away from a specified original location.
- 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7cd6b98819080898934552a72f9 |
completed | March 1, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69a4a5133bf88190a613e96d1f7cffa7 |
completed | March 1, 2026, 8:44 p.m. |
| PDg | Predicate description generation | batch_69a4a58c0a84819094f07658dc651b36 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:38 p.m.