Triple
T29421174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siniristilippu |
E746159
|
entity |
| Predicate | usesCrossType |
P67845
|
FINISHED |
| Object | Nordic cross |
—
|
NE NERFINISHED |
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: [Siniristilippu, usesCrossType, Nordic cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCrossType Context triple: [Siniristilippu, usesCrossType, Nordic cross]
-
A.
crossType
Indicates a relationship where one entity intersects, passes over, or traverses another, typically implying movement or extension across a boundary, area, or medium.
-
B.
hasTypeOfCross
chosen
Indicates that an entity possesses or is associated with a specific type or style of cross.
-
C.
hasCross
Indicates that one entity possesses, displays, or is marked by a cross in relation to another entity or context.
-
D.
usedCross
Indicates that one entity made use of a cross-shaped object or structure, or traversed by means of a crossing point such as a crosswalk or intersection.
-
E.
centralCrossType
Indicates the specific form or design of the cross located at the central position of an object or structure.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 28, 2026, 3:05 p.m.