Triple
T3170409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Something Good |
E66316
|
entity |
| Predicate | includedInLaterStageRevisions |
P46724
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Something Good, includedInLaterStageRevisions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedInLaterStageRevisions Context triple: [Something Good, includedInLaterStageRevisions, yes]
-
A.
includesChangeHistory
Indicates that the subject maintains or contains a record of past modifications or changes made to it.
-
B.
isUpdatedThrough
Indicates that one entity’s state or content is modified or brought up to date as a result of a process, action, or interaction involving another entity.
-
C.
updatedWithEachVersionOf
Indicates that something is modified or revised every time a new version of another entity is released.
-
D.
isTemporaryVersionOf
Indicates that one entity is a non-final, short-lived or provisional form of another, more permanent entity.
-
E.
revisionKnownAs
Indicates that a particular revision of an entity is referred to or identified by a specific alternative name or label.
- 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada64917e08190bf0466d2c5e43790 |
completed | March 8, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0076b4819094628f1ad10b8f68 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada20880e481908ecac09d49b1f1c3 |
completed | March 8, 2026, 4:21 p.m. |
Created at: March 8, 2026, 3:06 p.m.