Triple
T22977646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mockingjay |
E571368
|
entity |
| Predicate | linkedToGesture |
P145626
|
FINISHED |
| Object | three-finger salute |
—
|
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: three-finger salute | Statement: [Mockingjay, linkedToGesture, three-finger salute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToGesture Context triple: [Mockingjay, linkedToGesture, three-finger salute]
-
A.
linkedToStatement
Indicates that one entity is associated or connected to a particular statement, typically as a reference, support, or contextual link.
-
B.
linkedToProperty
Indicates that one entity is associated or connected to a specific property or attribute of another entity.
-
C.
linkedToObject
chosen
Indicates that one entity is connected or associated with another entity in some meaningful way.
-
D.
linkedToPort
Indicates that one entity is connected or associated with a specific port, such as a network, hardware, or interface port.
-
E.
linkedLocation
Indicates that one location is associated or connected to another location in a meaningful way, such as being related, referenced, or contextually tied.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18292f3788190ab4e9d559e0070c8 |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:48 p.m.