Triple
T5563820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flag of Egypt |
E145830
|
entity |
| Predicate | emblemHolds |
P8639
|
FINISHED |
| Object | scroll with the official name of the state in Arabic |
—
|
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: scroll with the official name of the state in Arabic | Statement: [flag of Egypt, emblemHolds, scroll with the official name of the state in Arabic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emblemHolds Context triple: [flag of Egypt, emblemHolds, scroll with the official name of the state in Arabic]
-
A.
emblemUsedBy
Indicates that a particular emblem is adopted or employed by a specific entity as its symbol or identifying mark.
-
B.
emblemName
Indicates that a specified name is the official or recognized title of an emblem.
-
C.
emblemStatus
Indicates the current state or condition of an emblem, such as whether it is active, valid, displayed, or in use.
-
D.
emblemFeatures
chosen
Indicates that an emblem includes or displays specific visual elements or characteristics.
-
E.
hasEmblemColor
Indicates that an emblem possesses or is characterized by a specific color.
- 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_69c008fdae24819081aa002ad99cd966 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02032330c819094f2bc1e8c93a5b6 |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.