Triple
T19077427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pierre Clerget |
E466939
|
entity |
| Predicate | usedEnginesIn |
P121358
|
FINISHED |
| Object | military aircraft of World War I |
—
|
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: military aircraft of World War I | Statement: [Pierre Clerget, usedEnginesIn, military aircraft of World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedEnginesIn Context triple: [Pierre Clerget, usedEnginesIn, military aircraft of World War I]
-
A.
previouslyUsedEngine
Indicates that an engine has been used before in a prior context or application, rather than being new or unused.
-
B.
engineUsedIn
chosen
Indicates that a particular engine is utilized as a component or power source within a specified system, device, or application.
-
C.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
D.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
E.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e5591081908a4f8e4b2011b408 |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.