Triple
T11192542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Lambert |
E264836
|
entity |
| Predicate | servesCommodity |
P92762
|
FINISHED |
| Object | iron ore |
—
|
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: iron ore | Statement: [Cape Lambert, servesCommodity, iron ore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesCommodity Context triple: [Cape Lambert, servesCommodity, iron ore]
-
A.
servesProduct
chosen
Indicates that one entity provides or offers a particular product to others, typically in a commercial or service context.
-
B.
servesType
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
C.
intendedToServe
Indicates that one entity was designed, planned, or purposed specifically to benefit, assist, or fulfill the needs of another entity.
-
D.
servesOn
Indicates that one entity performs duties, functions, or holds a role as a member within another entity, such as a group, body, or organization.
-
E.
isServed
Indicates that one entity provides or delivers a service, product, or assistance to 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8be025481909d311b587418dfb2 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.