Triple
T14471552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mortimer |
E358853
|
entity |
| Predicate | hasCommuterLinks |
P114783
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mortimer, hasCommuterLinks, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommuterLinks Context triple: [Mortimer, hasCommuterLinks, true]
-
A.
hasCommuterPattern
Indicates that there is a characteristic or recurring pattern in how an entity regularly travels between locations, typically for work or daily activities.
-
B.
hasCommuterTraffic
Indicates that there is regular, recurring traffic flow associated with people traveling between their homes and places of work or study.
-
C.
hasCommuterOrientation
Indicates that an entity is designed or intended primarily for use by commuters, emphasizing suitability for regular travel between home and work or study.
-
D.
hasMajorRailLinksTo
Indicates that there are significant railway connections or routes between two locations.
-
E.
includesCommuterSystem
Indicates that one entity contains or incorporates a commuter transportation system as part of its structure or services.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91f969788190a5114f92d7159aae |
completed | April 14, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de610330a48190b558235a14c0dc9f |
completed | April 14, 2026, 3:45 p.m. |
Created at: April 10, 2026, 1:20 a.m.