Triple
T38226048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Penrhyn |
E1012148
|
entity |
| Predicate | principalShippingPointFor |
P106230
|
FINISHED |
| Object | Penrhyn Quarry |
—
|
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: Penrhyn Quarry | Statement: [Port Penrhyn, principalShippingPointFor, Penrhyn Quarry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: principalShippingPointFor Context triple: [Port Penrhyn, principalShippingPointFor, Penrhyn Quarry]
-
A.
primaryFreightDestination
Indicates the main location to which freight is intended to be shipped or delivered.
-
B.
ownedShippingLine
Indicates that one entity possessed legal ownership or controlling interest in a particular shipping line.
-
C.
primaryCouriersAssociated
Indicates that certain couriers are designated as the main or primary delivery agents associated with a given entity or context.
-
D.
oreShippedTo
chosen
Indicates that ore is transported or delivered from one location or entity to another.
-
E.
primaryExchangeLocation
Indicates the main place or venue where the exchange or transaction between the related entities primarily occurs.
- 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.