Triple
T13271424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toku Ro.2 (KR10) |
E316066
|
entity |
| Predicate | powering |
P109257
|
FINISHED |
| Object | single-seat fighter aircraft |
—
|
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: single-seat fighter aircraft | Statement: [Toku Ro.2 (KR10), powering, single-seat fighter aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powering Context triple: [Toku Ro.2 (KR10), powering, single-seat fighter aircraft]
-
A.
inPower
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
-
B.
poweringTitle
Indicates that one entity serves as the primary driving force, enabler, or underlying support behind the title, role, or status of another entity.
-
C.
enablingPowerFor
Indicates that one entity provides the capability or authority that allows another entity to perform a specific function, action, or role.
-
D.
powerPack
Indicates that one entity serves as a power pack or portable power source for another entity.
-
E.
powerFeeding
Indicates a relationship where one entity supplies electrical power to another entity for its operation or charging.
- F. None of above. chosen
Provenance (4 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:26 p.m.