Triple
T19500493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erfalasorput |
E487888
|
entity |
| Predicate | flagElement |
P136155
|
FINISHED |
| Object | off-center disk |
—
|
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: off-center disk | Statement: [Erfalasorput, flagElement, off-center disk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagElement Context triple: [Erfalasorput, flagElement, off-center disk]
-
A.
flagOrInsignia
Indicates that one entity serves as a flag, emblem, or insignia representing another entity.
-
B.
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.
-
C.
flagFlown
Indicates that a particular flag is being displayed or flown at a specific location or by a specific entity.
-
D.
flagDesign
Indicates the relationship in which one entity is responsible for creating, specifying, or defining the design of a flag associated with another entity.
-
E.
flagFamily
Indicates that one flag is part of, or associated with, a broader family or group of related flags.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6350ce7cc819086d77bbd9cd52b53 |
completed | April 20, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004d3a708190a1c13c8f644f3926 |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:40 p.m.