Triple
T18719572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YARTS |
E457732
|
entity |
| Predicate | acronym |
P43
|
FINISHED |
| Object | YARTS |
E457732
|
NE 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: YARTS | Statement: [YARTS, acronym, YARTS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: YARTS Context triple: [YARTS, acronym, YARTS]
-
A.
YARTS
chosen
YARTS is a public transit service that provides bus transportation to and within Yosemite National Park and surrounding communities in California.
-
B.
YAKT
YAKT is the time zone abbreviation for Yakutsk Time, used in parts of eastern Russia.
-
C.
YRT
YRT is the IATA airport code for Rankin Inlet Airport, a key air transport hub serving the community of Rankin Inlet in Nunavut, Canada.
-
D.
YRT
YRT is the public transit system serving Ontario’s York Region, operating local and rapid buses that connect communities north of Toronto.
-
E.
YAK
YAK is the IATA airport code for Yakutat Airport, a public airport serving the community of Yakutat in Alaska, United States.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56ab90adc81909f3b4aabb6d5a707 |
completed | April 19, 2026, 11:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a052b453368819082e56ed1e8c13e21 |
completed | May 14, 2026, 1:54 a.m. |
Created at: April 10, 2026, 11:50 a.m.