Triple
T21085829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngembak Geni |
E519483
|
entity |
| Predicate | resumptionOf |
P7824
|
FINISHED |
| Object | public activities |
—
|
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: public activities | Statement: [Ngembak Geni, resumptionOf, public activities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resumptionOf Context triple: [Ngembak Geni, resumptionOf, public activities]
-
A.
resumedIn
Indicates that an activity, process, or state that was previously paused or interrupted has started again within or at a specified context, time, or location.
-
B.
resumesAfter
chosen
Indicates that an activity, process, or state starts again following a pause, interruption, or completion of another specified event.
-
C.
constructionResumed
Indicates that previously halted construction activity on an entity or project has started again.
-
D.
resumedCouncil
Indicates that a council or formal deliberative body has restarted its meetings or proceedings after a pause or interruption.
-
E.
resumptionYear
Indicates the year in which an activity, process, or state that was previously halted starts again.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094ad1c08190a4b9d2668a6362b2 |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:50 p.m.