Triple
T6205537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordic cross flags |
E138734
|
entity |
| Predicate | sharesDesignConventionWith |
P8153
|
FINISHED |
| Object | Nordic naval ensigns |
—
|
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 naval ensigns | Statement: [Nordic cross flags, sharesDesignConventionWith, Nordic naval ensigns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesDesignConventionWith Context triple: [Nordic cross flags, sharesDesignConventionWith, Nordic naval ensigns]
-
A.
sharesDesignationTypeWith
Indicates that two entities have the same type or category of designation (e.g., title, label, or classification).
-
B.
sharesDesignTraditionWith
chosen
Indicates that two entities originate from or participate in the same design tradition, sharing common stylistic principles, methods, or heritage.
-
C.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
D.
sharesRulesWith
Indicates that two entities follow, are governed by, or operate under the same set of rules or regulations.
-
E.
sharesNameWith
Indicates that two entities have the same name or an identical naming designation.
- 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0626f85748190a94448117a85fd78 |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.