Triple
T35264545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sailing Ship Columbia |
E1018469
|
entity |
| Predicate | homePortInPark |
P90743
|
FINISHED |
| Object | Frontierland dock |
—
|
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: Frontierland dock | Statement: [Sailing Ship Columbia, homePortInPark, Frontierland dock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homePortInPark Context triple: [Sailing Ship Columbia, homePortInPark, Frontierland dock]
-
A.
homePort
Indicates that a vessel or mobile entity is based at, registered to, or primarily operates from a particular port or harbor.
-
B.
positionInPark
chosen
Indicates that one entity occupies a specific location or spot within a park.
-
C.
inPark
Indicates that one entity is located within or inside the boundaries of a park.
-
D.
startingPark
Indicates that an entity begins or initiates its activity, route, or presence from a specified park.
-
E.
laterHomePort
Indicates that one location served as the subsequent or later home port of a vessel or entity after an earlier home port.
- 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_69f76de4be5c8190a51705c07612cac8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f75541481908e09847e6dfac6c4 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.