Triple
T36997542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of the President of Iceland |
E915268
|
entity |
| Predicate | crossStyle |
P192255
|
FINISHED |
| Object | Nordic cross |
—
|
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: Nordic cross | Statement: [Flag of the President of Iceland, crossStyle, Nordic cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossStyle Context triple: [Flag of the President of Iceland, crossStyle, Nordic cross]
-
A.
crossingStyle
Indicates the manner or method by which one entity crosses or traverses another (such as a boundary, path, or medium).
-
B.
crossType
Indicates a relationship where one entity intersects, passes over, or traverses another, typically implying movement or extension across a boundary, area, or medium.
-
C.
crossWith
Indicates that one entity intersects or passes over/through the path, boundary, or position of another entity.
-
D.
crossStructure
Indicates that one entity passes over, through, or across the physical span or boundary defined by another structure.
-
E.
crossCut
Indicates that one entity intersects or passes through another, typically cutting across it from one side to the other.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69fd026757a081909911a59a78652709 |
completed | May 7, 2026, 9:21 p.m. |
Created at: May 3, 2026, 4:14 p.m.