Triple
T343112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Powell–Mason line |
E6879
|
entity |
| Predicate | primaryRiders |
P12077
|
FINISHED |
| Object | tourists |
—
|
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: tourists | Statement: [Powell–Mason line, primaryRiders, tourists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRiders Context triple: [Powell–Mason line, primaryRiders, tourists]
-
A.
primaryTraction
Indicates that one entity serves as the main source or means of traction, pulling power, or driving force for another entity or process.
-
B.
primaryUser
Indicates that the referenced user is the main or principal user associated with a given account, resource, or context.
-
C.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
-
D.
primaryBeneficiaries
Indicates which entities are the main recipients or advantaged parties resulting from a particular action, resource, or arrangement.
-
E.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb0019088190a9b969c4287dc4fa |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e9530c98819085025efe4e04aa7e |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea0a4c448190a8a179daa9b90645 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.