Triple
T22747112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saltaire |
E562581
|
entity |
| Predicate | primaryInternalTransport |
P149591
|
FINISHED |
| Object | walking |
—
|
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: walking | Statement: [Saltaire, primaryInternalTransport, walking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryInternalTransport Context triple: [Saltaire, primaryInternalTransport, walking]
-
A.
primaryTransport
Indicates that one entity serves as the main or most commonly used means of transportation for another entity.
-
B.
internalOutcome
Indicates an outcome or result that arises from within an entity, system, or process itself, rather than from external factors.
-
C.
primaryTransmission
Indicates the main or original transfer of something (such as information, energy, or disease) from one source entity to another.
-
D.
primaryBus
Indicates that one entity functions as the main or principal bus associated with another entity within a system or configuration.
-
E.
primaryProtocol
Indicates that one protocol is designated as the main or default protocol used in a given context or interaction.
- 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_69e245513a5c81908d5cb471b4fc429d |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179b634b88190906edd92a971f921 |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:24 p.m.