Triple
T34241206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firefang |
E878470
|
entity |
| Predicate | associatedConfiguration |
P205379
|
FINISHED |
| Object | twin-engine fighter |
—
|
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: twin-engine fighter | Statement: [Firefang, associatedConfiguration, twin-engine fighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedConfiguration Context triple: [Firefang, associatedConfiguration, twin-engine fighter]
-
A.
associatedSystem
Indicates that one entity is functionally or contextually linked to a particular system with which it interacts or to which it belongs.
-
B.
associatedItem
Indicates that one item is linked or connected to another in a relevant or context-dependent way, without specifying a more precise relationship.
-
C.
associatedFort
Indicates that one entity is connected or linked to a particular fort, typically as its related or corresponding fortification.
-
D.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
E.
associatedWithSetting
Indicates that one entity is connected or linked to a particular context, environment, or setting in which it occurs or is relevant.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:56 a.m.