Triple
T24103764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ortiz Wharf |
E597157
|
entity |
| Predicate | isMajorRole |
P101358
|
FINISHED |
| Object | key passenger and cargo pier in Iloilo City |
—
|
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: key passenger and cargo pier in Iloilo City | Statement: [Ortiz Wharf, isMajorRole, key passenger and cargo pier in Iloilo City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorRole Context triple: [Ortiz Wharf, isMajorRole, key passenger and cargo pier in Iloilo City]
-
A.
isMajor
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
B.
isMajorFor
Indicates that one entity serves as the primary field of academic specialization (major) for another entity, typically a student.
-
C.
isKeyRole
chosen
Indicates that an entity holds a primary or critically important role within a given context or structure.
-
D.
isMajorSeeWithin
Indicates that one entity is the primary or most significant location or area encompassed within the boundaries of another entity.
-
E.
isMajorStandOf
Indicates that one entity is the primary or most significant stand or display associated with another entity.
- 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de1399108190986f604468cd5858 |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11 p.m.