Triple
T12390948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Georg von Trapp (The Sound of Music) |
E295990
|
entity |
| Predicate | initiallyUses |
P6318
|
FINISHED |
| Object | whistle to summon his children |
—
|
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: whistle to summon his children | Statement: [Captain Georg von Trapp (The Sound of Music), initiallyUses, whistle to summon his children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiallyUses Context triple: [Captain Georg von Trapp (The Sound of Music), initiallyUses, whistle to summon his children]
-
A.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
B.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
-
C.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
-
D.
firstUsedFor
chosen
Indicates that one entity was the earliest or original thing for which another entity was used or applied.
-
E.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fd0bcc48190bb1a59a3aaa6bfdf |
completed | April 10, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.