Triple
T2911547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jericho-Trompete siren |
E63692
|
entity |
| Predicate | activationMode |
P38751
|
FINISHED |
| Object | mechanically driven by airflow |
—
|
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: mechanically driven by airflow | Statement: [Jericho-Trompete siren, activationMode, mechanically driven by airflow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activationMode Context triple: [Jericho-Trompete siren, activationMode, mechanically driven by airflow]
-
A.
activationMechanism
chosen
Indicates the process or method by which one entity initiates, triggers, or enables the activity or functioning of another entity.
-
B.
activationTime
Indicates the specific point in time at which an entity, process, or function becomes active or starts operating.
-
C.
activationAuthority
Indicates the entity that has the power or permission to initiate or activate a specified process, function, or resource.
-
D.
registrationMode
Indicates the method or process by which something is registered or enrolled.
-
E.
activeFrom
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0ea0ae4819096f17d74072b0b78 |
completed | March 7, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69abdd1b77608190b20fc078fdb85e64 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:11 p.m.