Triple
T14320117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klais pipe organ |
E355061
|
entity |
| Predicate | typicalActionType |
P107993
|
FINISHED |
| Object | mechanical action |
—
|
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: mechanical action | Statement: [Klais pipe organ, typicalActionType, mechanical action]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalActionType Context triple: [Klais pipe organ, typicalActionType, mechanical action]
-
A.
typicalInteraction
Indicates the usual or most common way in which two entities interact or relate to each other.
-
B.
typicalEvent
Indicates that the associated event is a common, characteristic, or prototypical occurrence for the given entity or situation.
-
C.
typicalTrigger
Indicates that one entity commonly or characteristically causes, initiates, or brings about the occurrence of another entity or event.
-
D.
typicalTask
chosen
Indicates the kind of task or activity that is normally or characteristically performed by an entity.
-
E.
causeOfAction
Indicates that one entity is the reason or basis for initiating a legal action or lawsuit against 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de883bf71c8190a9a092a025cf98f0 |
completed | April 14, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:13 a.m.