Triple
T10459787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subtitle III—General and Intermodal Programs |
E246640
|
entity |
| Predicate | codeTitleName |
P94161
|
FINISHED |
| Object | Transportation |
—
|
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: Transportation | Statement: [Subtitle III—General and Intermodal Programs, codeTitleName, Transportation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeTitleName Context triple: [Subtitle III—General and Intermodal Programs, codeTitleName, Transportation]
-
A.
namedForTitle
Indicates that one entity is named after or in honor of the title (such as a rank, honorific, or formal designation) associated with another entity.
-
B.
columnTitle
Indicates that one entity serves as the title or header label for a column associated with another entity.
-
C.
commonTitle
Indicates that two or more entities share the same title or designation.
-
D.
cultTitleOf
Indicates that the subject holds a religious or cultic title or honorific associated with the object.
-
E.
builderTitle
Indicates the formal title or designation held by a person or entity in their role as a builder.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50882eb0c8190a4311634b867eab1 |
completed | April 7, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:18 p.m.