Triple
T22392852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Trooper |
E553549
|
entity |
| Predicate | hasSignatureStageProp |
P140478
|
FINISHED |
| Object | Union Jack flag waved by vocalist |
—
|
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: Union Jack flag waved by vocalist | Statement: [The Trooper, hasSignatureStageProp, Union Jack flag waved by vocalist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignatureStageProp Context triple: [The Trooper, hasSignatureStageProp, Union Jack flag waved by vocalist]
-
A.
hasSignatureStatusFor
Indicates that a specific entity holds or is assigned a particular signature-related status in relation to another entity or context.
-
B.
hasSignProperty
chosen
Indicates that an entity possesses a specific sign-related characteristic or attribute.
-
C.
hasSignatureTrait
Indicates that an entity possesses a defining or characteristic trait that is especially distinctive or representative of it.
-
D.
hasSignatureEvent
Indicates that an entity is associated with a distinctive or defining event that characterizes or highlights it.
-
E.
hasSignatureRole
Indicates that an entity holds a primary, defining, or officially recognized role within a given context or relationship.
- 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1585c16188190872e75caeb86c328 |
completed | April 29, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.