Triple
T5725293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodside |
E126249
|
entity |
| Predicate | isKeyTransferPoint |
P20129
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Woodside, isKeyTransferPoint, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyTransferPoint Context triple: [Woodside, isKeyTransferPoint, yes]
-
A.
isKeyTransitHub
Indicates that a location functions as a major transfer point where multiple transportation routes or modes intersect and a high volume of passenger or cargo movement is concentrated.
-
B.
isKeyEndpointOf
Indicates that one endpoint in a connection, link, or structure serves as the primary or designated key endpoint of the other.
-
C.
isKeyInterchangeFor
chosen
Indicates that one location or facility serves as a primary transfer point connecting major routes, lines, or modes of transport for another.
-
D.
isReferencePointFor
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
-
E.
isKeyRegionFor
Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger area.
- 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_69c0082f723881908ce8bb13a0c0f8b7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c6488881909bed4a4534d57f70 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:47 p.m.