Triple
T5954607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landmark Mall site |
E132480
|
entity |
| Predicate | transportationOrientation |
P28994
|
FINISHED |
| Object | transit-oriented |
—
|
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: transit-oriented | Statement: [Landmark Mall site, transportationOrientation, transit-oriented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportationOrientation Context triple: [Landmark Mall site, transportationOrientation, transit-oriented]
-
A.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
B.
transportationContext
chosen
Indicates the situational or environmental conditions under which transportation occurs, such as mode, purpose, or circumstances of travel.
-
C.
transportationReference
Indicates that one entity serves as a reference or identifier for a specific mode, instance, or detail of transportation associated with another entity.
-
D.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
E.
transportCorridor
Indicates a route or pathway used to move people, goods, or resources between locations.
- 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_69c0086b05cc8190a8f36a96927a525c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03fb7f8a88190a8bd45208bda4a03 |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0335a635881909c58c1ef0f97f1e8 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:02 p.m.