Triple
T23008351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Percy Pilcher |
E572838
|
entity |
| Predicate | plannedToBuild |
P24655
|
FINISHED |
| Object | powered flying machine |
—
|
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: powered flying machine | Statement: [Percy Pilcher, plannedToBuild, powered flying machine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedToBuild Context triple: [Percy Pilcher, plannedToBuild, powered flying machine]
-
A.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
B.
seeksToBuild
chosen
Indicates an intention or effort by one entity to create, develop, or establish something.
-
C.
plannedDevelopment
Indicates that one entity has been designated or scheduled for future development or construction by another entity.
-
D.
planned
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
-
E.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1835919b08190ba78e182b87358d4 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.