Triple
T25940696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsitsistas |
E653688
|
entity |
| Predicate | hasFlagOrSymbol |
P160955
|
FINISHED |
| Object | Cheyenne tribal flag |
—
|
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: Cheyenne tribal flag | Statement: [Tsitsistas, hasFlagOrSymbol, Cheyenne tribal flag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlagOrSymbol Context triple: [Tsitsistas, hasFlagOrSymbol, Cheyenne tribal flag]
-
A.
hasFlagName
Indicates that an entity is associated with or identified by a specific flag name.
-
B.
hasSymbolFor
Indicates that one entity serves as the symbolic representation or sign for another entity.
-
C.
hasColorSymbol
Indicates that one entity is associated with another entity that serves as its representative or symbolic color.
-
D.
hasPropertyFlag
Indicates that an entity possesses a specific property denoted by a particular flag or marker.
-
E.
hasSettingSymbol
Indicates that one entity uses or is associated with another entity as a symbolic representation of its setting or environment.
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60dfaeebc8190ac01d3a0030acf55 |
completed | May 2, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60c68b02c8190870758d79cdec68b |
completed | May 2, 2026, 2:38 p.m. |
Created at: April 22, 2026, 8:40 a.m.