Triple
T869027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury |
E18768
|
entity |
| Predicate | transitFrequencyApprox |
P20359
|
FINISHED |
| Object | about 13 times per century |
—
|
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: about 13 times per century | Statement: [Mercury, transitFrequencyApprox, about 13 times per century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitFrequencyApprox Context triple: [Mercury, transitFrequencyApprox, about 13 times per century]
-
A.
hasPublicTransportConnection
Indicates that there is an available public transportation link or service connecting the related entities.
-
B.
isOneOfBusiestStopsOn
Indicates that a stop ranks among the most heavily used or frequently served stops on a given route or line.
-
C.
hasAdjacentBusStation
Indicates that one location has a bus station situated directly next to or very near it.
-
D.
transportReliability
Indicates how consistently and dependably a transport service or system performs as expected over time.
-
E.
hasBusInterchange
Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac811e548190a72b7a10b5ea8665 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa87504481909618a6815948da6f |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab498bb0819080e3afb684b504b6 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.