Triple
T29624022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norfolk Island flag |
E755079
|
entity |
| Predicate | vexillologicalSymbol |
P167524
|
FINISHED |
| Object | Norfolk Island pine |
—
|
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: Norfolk Island pine | Statement: [Norfolk Island flag, vexillologicalSymbol, Norfolk Island pine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vexillologicalSymbol Context triple: [Norfolk Island flag, vexillologicalSymbol, Norfolk Island pine]
-
A.
vexillologicalCategory
Indicates the classification of something within a specific category or type used in the study of flags.
-
B.
vexillologyCode
Indicates a standardized code or classification assigned within the context of flags or the study of flags (vexillology).
-
C.
vexillologyNotability
Indicates that an entity is notable or significant specifically in the field or context of vexillology (the study of flags).
-
D.
religiousSymbolOnFlag
Indicates that a flag features a symbol associated with a religion as part of its design.
-
E.
flagOrInsignia
Indicates that one entity serves as a flag, emblem, or insignia representing another entity.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66e26eda081908c514b28a814b250 |
completed | May 2, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:36 p.m.