Triple
T38188798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Manchester |
E1005393
|
entity |
| Predicate | hasSecondaryMode |
P90082
|
FINISHED |
| Object | road |
—
|
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: road | Statement: [London–Manchester, hasSecondaryMode, road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryMode Context triple: [London–Manchester, hasSecondaryMode, road]
-
A.
hasSecondaryUsage
Indicates that an entity is associated with an additional, non-primary function or purpose beyond its main intended use.
-
B.
hasSecondary
chosen
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
C.
hasSecondaryCore
Indicates that an entity possesses an additional, subordinate core component alongside its primary core.
-
D.
hasTertiaryMode
Indicates that an entity possesses or is associated with a third-level or tertiary mode, method, or operational state within a set of possible modes.
-
E.
hasPrimaryModeSupported
Indicates that an entity supports a particular mode as its main or default mode of operation.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00c07b302081908bf9755f8fdbc36e |
completed | May 10, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_6a00bfffb168819084b65804d601896d |
completed | May 10, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:29 p.m.