Triple
T5371287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clayton Vale |
E108854
|
entity |
| Predicate | hasReclamationHistory |
P63604
|
FINISHED |
| Object | former industrial land |
—
|
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: former industrial land | Statement: [Clayton Vale, hasReclamationHistory, former industrial land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReclamationHistory Context triple: [Clayton Vale, hasReclamationHistory, former industrial land]
-
A.
hasRelegationHistory
Indicates that an entity has experienced one or more relegations in its competitive or hierarchical history.
-
B.
hasSettlementHistory
Indicates that an entity has a documented history of human settlement or habitation in relation to another entity (such as a place or time period).
-
C.
hasDenominationHistory
Indicates that an entity has an associated record or sequence of changes in its denomination over time.
-
D.
hasTransportHistoryAs
Indicates that an entity has a record or log of being transported, characterized or classified in a specific way.
-
E.
ownershipHistory
Indicates the sequence of past and present owners associated with an entity over time.
- F. None of above. chosen
Provenance (4 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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd887f5b0081909456992d1a071928 |
completed | March 20, 2026, 5:48 p.m. |
Created at: March 20, 2026, 2:02 p.m.