Triple
T28310215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PTR-91 |
E713972
|
entity |
| Predicate | typicalTriggerSystem |
P68427
|
FINISHED |
| Object | hammer-fired |
—
|
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: hammer-fired | Statement: [PTR-91, typicalTriggerSystem, hammer-fired]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTriggerSystem Context triple: [PTR-91, typicalTriggerSystem, hammer-fired]
-
A.
typicalTrigger
Indicates that one entity commonly or characteristically causes, initiates, or brings about the occurrence of another entity or event.
-
B.
usesTriggerSystem
chosen
Indicates that one entity operates or functions by means of a trigger-based mechanism or system provided or associated with another entity.
-
C.
trapTrigger
Indicates that an entity activates or sets off a trap in the environment.
-
D.
typicalInductionSystem
Indicates that one entity is a standard or representative example of an induction system associated with another entity.
-
E.
trigger
Indicates that one entity causes or initiates an event, state, or action in another entity or system.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_6a0087de41c48190b2743a26b6d65409 |
completed | May 10, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_6a00870a8bc48190be1385579b8cc1dd |
completed | May 10, 2026, 1:24 p.m. |
Created at: April 27, 2026, 11:40 p.m.