Triple
T8569193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pressure Machine |
E202882
|
entity |
| Predicate | hasIntroductorySpokenWord |
P56242
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pressure Machine, hasIntroductorySpokenWord, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntroductorySpokenWord Context triple: [Pressure Machine, hasIntroductorySpokenWord, true]
-
A.
hasSpokenWordIntro
chosen
Indicates that an entity includes or features an introductory segment performed in spoken word form.
-
B.
isSpokenAlong
Indicates that something (typically a language or dialect) is used or spoken in the regions or areas that follow a particular path, boundary, or route.
-
C.
hasLiveSpokenIntroductions
Indicates that one entity provides live, spoken introductory remarks or presentations for another entity or event.
-
D.
isSpoken
Indicates that a language or utterance is produced orally by a speaker or used in spoken form within a given context.
-
E.
hasIntroduction
Indicates that one entity includes or provides an introductory section, part, or presentation for 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_69ca8327b0a881908606ff860713964d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea3f28608190a07be8b324669a12 |
completed | March 31, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:21 p.m.