Triple
T135630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esperanto |
E2739
|
entity |
| Predicate | hasOfficialFlag |
P754
|
FINISHED |
| Object | green flag with white square and green star |
—
|
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: green flag with white square and green star | Statement: [Esperanto, hasOfficialFlag, green flag with white square and green star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialFlag Context triple: [Esperanto, hasOfficialFlag, green flag with white square and green star]
-
A.
nationalFlag
chosen
Indicates that one entity is the official national flag representing the other entity (a country or nation).
-
B.
hasNationalSymbol
Indicates that an entity possesses or is associated with an officially recognized national symbol of a country or nation.
-
C.
hasOfficialInsigniaLocation
Indicates the specific place where an entity’s official insignia is physically located or displayed.
-
D.
nationalFlagColor
Indicates that a specific color appears on the national flag of a given country.
-
E.
flag
Indicates that one entity marks, signals, or draws attention to another entity, often to denote status, importance, or the need for review or action.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a3ad908190b6a8652f09ae0cbb |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a25651b9048190a6277b7fec98c1ea |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.