Triple
T11892003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overseas Passenger Terminal |
E282938
|
entity |
| Predicate | mainFor |
P18495
|
FINISHED |
| Object | Sydney cruise ship operations |
—
|
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: Sydney cruise ship operations | Statement: [Overseas Passenger Terminal, mainFor, Sydney cruise ship operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainFor Context triple: [Overseas Passenger Terminal, mainFor, Sydney cruise ship operations]
-
A.
mainRite
Indicates that one ritual, ceremony, or rite is the primary or central rite associated with a given context, entity, or event.
-
B.
mainFunctions
chosen
Indicates that the subject serves as the primary or central functional component or role for the object.
-
C.
mainBoardFor
Indicates that one entity serves as the primary circuit board or central board used by another entity.
-
D.
mainSingle
Indicates that an entity is the primary or sole main instance among a set of related entities.
-
E.
mainEntranceOn
Indicates that the primary entrance of one entity is located on or faces toward another entity, such as a particular side, street, or boundary.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a3f7548190adfb567f060a175a |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.