Triple
T37906881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland |
E945578
|
entity |
| Predicate | hasAerialTram |
P189604
|
FINISHED |
| Object | Portland Aerial Tram |
—
|
NE NERFINISHED |
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: Portland Aerial Tram | Statement: [Portland, hasAerialTram, Portland Aerial Tram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAerialTram Context triple: [Portland, hasAerialTram, Portland Aerial Tram]
-
A.
hasCableCar
Indicates that one entity possesses, operates, or is served by a cable car system connecting it to other locations or points.
-
B.
hasSkiLiftType
Indicates the specific type or category of ski lift associated with an entity.
-
C.
hasSkiLifts
Indicates that one location or facility is equipped with ski lifts that provide transportation for skiers or visitors.
-
D.
hasRopewayTerminal
Indicates that one entity serves as or contains a ropeway (cable car) terminal associated with another entity.
-
E.
hasFunicular
Indicates that one place or facility is equipped with or served by a funicular railway connection to another location.
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:20 p.m.