Triple
T15938776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayraktar TB2 |
E386505
|
entity |
| Predicate | enduranceClass |
P30014
|
FINISHED |
| Object | long-endurance |
—
|
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: long-endurance | Statement: [Bayraktar TB2, enduranceClass, long-endurance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enduranceClass Context triple: [Bayraktar TB2, enduranceClass, long-endurance]
-
A.
endurance
chosen
Indicates the capacity of an entity to sustain an activity, state, or condition over an extended period without failure or significant loss of performance.
-
B.
speedClass
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
-
C.
endures
Indicates that an entity continues to exist, persist, or remain in a particular state or condition over a period of time, often despite challenges or changes.
-
D.
competitionClass
Indicates that one entity is classified into a particular competitive category or level within a competition or contest.
-
E.
designedToOutrun
Indicates that one entity was intentionally created or engineered with the capability to move faster than 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.