Triple
T11820248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mischief Reef |
E281105
|
entity |
| Predicate | reclamationEndApprox |
P56577
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Mischief Reef, reclamationEndApprox, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reclamationEndApprox Context triple: [Mischief Reef, reclamationEndApprox, 2016]
-
A.
reconstructionEndDate
Indicates the date on which a reconstruction process or project is completed.
-
B.
redevelopmentEnd
chosen
Indicates the point in time or event at which a redevelopment process or project is considered completed or ceases.
-
C.
rethemendFrom
Indicates that something is recommended or endorsed based on or derived from another source or entity.
-
D.
approximateEndUse
Indicates that something is an estimated or inferred final purpose, application, or consumption context of another entity.
-
E.
rebuiltEnd
Indicates that one entity has been reconstructed, restored, or rebuilt at the endpoint or conclusion of another entity or process.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e87e488190905bc3bb6d721e56 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.