Triple
T28713732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HandyDART |
E729893
|
entity |
| Predicate | regionTransitAuthority |
P20657
|
FINISHED |
| Object | TransLink |
—
|
NE NERFINISHED |
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: TransLink | Statement: [HandyDART, regionTransitAuthority, TransLink]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionTransitAuthority Context triple: [HandyDART, regionTransitAuthority, TransLink]
-
A.
countryTransportAuthority
Indicates that a given authority or organization is responsible for overseeing, regulating, or managing transportation systems within a specific country.
-
B.
transitAuthorityAbbreviation
Indicates that one entity is the standard abbreviated form of the name of a particular transit authority.
-
C.
transportAuthorityType
Indicates the specific kind or category of authority responsible for overseeing or regulating transportation.
-
D.
roadTransportAuthority
Indicates that an entity serves as the official authority responsible for regulating, managing, or overseeing road transportation for another entity or area.
-
E.
hasPublicTransportAgency
chosen
Indicates that a place or transport system is served, managed, or overseen by a specific public transportation agency.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: April 28, 2026, 5:49 a.m.