Triple
T35264534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sailing Ship Columbia |
E1018469
|
entity |
| Predicate | showRole |
P127654
|
FINISHED |
| Object | pirate ship in Fantasmic! |
—
|
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: pirate ship in Fantasmic! | Statement: [Sailing Ship Columbia, showRole, pirate ship in Fantasmic!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showRole Context triple: [Sailing Ship Columbia, showRole, pirate ship in Fantasmic!]
-
A.
displayRole
Indicates the role or position an entity holds in the context of how it is presented or shown in a display.
-
B.
testRole
Indicates that an entity is assigned or associated with a specific role used for testing or validation purposes.
-
C.
showFormatRole
chosen
Indicates the role or function that an entity has in relation to the format of a show or presentation.
-
D.
representedRole
Indicates that one entity serves as a stand-in, proxy, or representative performing a role on behalf of another entity.
-
E.
showdown!Role
Indicates a role or function that an entity assumes or performs within the context of a showdown or competitive confrontation.
- 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.