Triple
T18687249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maungakiekie |
E456899
|
entity |
| Predicate | treeRemovedIn |
P132282
|
FINISHED |
| Object | 2000s |
—
|
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: 2000s | Statement: [Maungakiekie, treeRemovedIn, 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treeRemovedIn Context triple: [Maungakiekie, treeRemovedIn, 2000s]
-
A.
roofRemovedIn
Indicates that the roof of an entity was removed during a specified time or within a particular temporal context.
-
B.
laterRemovedTo
Indicates that an entity was moved or transferred to a location or state at a later time, after an earlier condition or placement.
-
C.
featureRemoved
Indicates that a previously existing feature has been taken out, disabled, or is no longer available.
-
D.
removedFrom
Indicates that one entity has been taken away, extracted, or detached from another entity or context.
-
E.
shrineRemovedIn
Indicates that a shrine was removed, dismantled, or no longer existed starting in the specified time or date.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b2d9a24819098c8e963ee430437 |
completed | April 19, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:49 a.m.