Triple
T31641947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wallasea Island |
E807479
|
entity |
| Predicate | receivesMaterialFrom |
P82280
|
FINISHED |
| Object | Crossrail tunnelling excavations |
—
|
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: Crossrail tunnelling excavations | Statement: [Wallasea Island, receivesMaterialFrom, Crossrail tunnelling excavations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesMaterialFrom Context triple: [Wallasea Island, receivesMaterialFrom, Crossrail tunnelling excavations]
-
A.
receivesCargoFrom
chosen
Indicates that one entity obtains or is delivered cargo from another entity.
-
B.
materialProvidedFor
Indicates that one entity supplies or makes available a material for use, processing, or incorporation by another entity or purpose.
-
C.
performedMaterialFrom
Indicates that an agent executed or presented a performance using or based on a particular material or source work.
-
D.
suppliedMaterialType
Indicates the type or category of material that is provided or supplied in a given context.
-
E.
recipientOf
Indicates that one entity is the receiver or beneficiary of something (such as an item, message, or action) from 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 30, 2026, 10:49 p.m.