Triple
T31290920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poolbeg chimneys |
E797938
|
entity |
| Predicate | safetyMarking |
P32294
|
FINISHED |
| Object | aviation warning markings |
—
|
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: aviation warning markings | Statement: [Poolbeg chimneys, safetyMarking, aviation warning markings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyMarking Context triple: [Poolbeg chimneys, safetyMarking, aviation warning markings]
-
A.
safetyLabel
chosen
Indicates that an entity has been assigned a safety-related classification or warning status.
-
B.
distinctiveMarking
Indicates that one entity bears a unique or distinguishing visual feature or pattern that sets it apart from others.
-
C.
mayHaveMarkings
Indicates that an entity is permitted or able to possess certain markings or distinguishing signs.
-
D.
armorMarkings
Indicates that one entity bears specific markings, patterns, or insignia on its armor in relation to another entity or context.
-
E.
lightingMarks
Indicates that one entity applies or provides lighting effects or illumination to another entity or location.
- 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_69f224dfde288190af313f3c221c857e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 29, 2026, 9:14 p.m.