Triple
T30841499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unfinished |
E785521
|
entity |
| Predicate | hasUnfinishedStatus |
P78572
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Unfinished, hasUnfinishedStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnfinishedStatus Context triple: [Unfinished, hasUnfinishedStatus, true]
-
A.
hasNotCompleted
chosen
Indicates that an entity has an expected task, process, or requirement that remains unfinished or not yet fulfilled.
-
B.
hasUnfinishedContinuation
Indicates that something currently has a continuation, sequel, or follow-up portion that exists or is planned but is not yet completed.
-
C.
hasUncededStatus
Indicates that a territory or land area has not been formally ceded, surrendered, or relinquished by its original governing or Indigenous authority.
-
D.
hasUnfinishedEnding
Indicates that an entity concludes in an incomplete, unresolved, or open-ended manner rather than reaching a fully finished state.
-
E.
hasOngoing
Indicates that one entity is currently engaged in, experiencing, or maintaining an activity, state, or process that has not yet concluded.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 29, 2026, 8:45 p.m.