Triple
T5902204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Åland |
E131253
|
entity |
| Predicate | belongsToFlagFamily |
P67227
|
FINISHED |
| Object | Scandinavian cross flags |
—
|
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: Scandinavian cross flags | Statement: [Flag of Åland, belongsToFlagFamily, Scandinavian cross flags]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToFlagFamily Context triple: [Flag of Åland, belongsToFlagFamily, Scandinavian cross flags]
-
A.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
B.
associatedWithFlag
Indicates a relationship where an entity is linked or connected to a particular flag, such as a national, organizational, or symbolic banner.
-
C.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
-
D.
belongsToFamilyCommonName
Indicates that an entity is associated with, or classified under, a particular family-level common name.
-
E.
associatedWithNumberOfFlags
Indicates a relationship where an entity is linked to a specific count or quantity of 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0334dc8248190b7394dcece362d52 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c0400dbec08190b2ef73689b2c0c31 |
completed | March 22, 2026, 7:16 p.m. |
Created at: March 22, 2026, 3:58 p.m.