Triple
T29439231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legacy |
E746664
|
entity |
| Predicate | notableLocationOnboard |
P71679
|
FINISHED |
| Object | monster cruise deck |
—
|
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: monster cruise deck | Statement: [Legacy, notableLocationOnboard, monster cruise deck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLocationOnboard Context triple: [Legacy, notableLocationOnboard, monster cruise deck]
-
A.
notableLocationOn
Indicates that a particular location is especially significant or noteworthy in relation to a specified entity or context.
-
B.
onboardLocation
chosen
Indicates that one entity is located on or within a vehicle, vessel, or other conveyance associated with another entity.
-
C.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
D.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
E.
notableLocationFeatured
Indicates that a particular location is prominently highlighted or showcased in relation to the subject.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a036054129081909e66c5d62015e6c1 |
completed | May 12, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_6a035f17cbf88190acd6bdbfc9789ffb |
completed | May 12, 2026, 5:10 p.m. |
Created at: April 28, 2026, 3:20 p.m.