Triple
T9309458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iraqi flag |
E223970
|
entity |
| Predicate | previousVersionIncluded |
P88000
|
FINISHED |
| Object | three green stars |
—
|
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: three green stars | Statement: [Iraqi flag, previousVersionIncluded, three green stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousVersionIncluded Context triple: [Iraqi flag, previousVersionIncluded, three green stars]
-
A.
previousVersionAdopted
Indicates that one entity has been adopted or implemented as a successor to an earlier version represented by the other entity.
-
B.
previousVersionModified
Indicates that a newer version of an entity has been created by modifying the specified previous version.
-
C.
hasEarlierVersion
Indicates that one entity is an earlier or prior version of another entity in a version sequence.
-
D.
previouslySupportedVersion
Indicates that one entity was a supported version of another entity at some time in the past but is no longer the current supported version.
-
E.
earlierVersionsCapability
Indicates that an entity has the ability to access, handle, or interact with earlier versions of another entity or resource.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd1daba67c819081d53545d67ef127 |
completed | April 1, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:37 p.m.