Triple
T33095215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farmer |
E846889
|
entity |
| Predicate | reportingNameCategory |
P154642
|
FINISHED |
| Object | fighter aircraft reporting name |
—
|
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: fighter aircraft reporting name | Statement: [Farmer, reportingNameCategory, fighter aircraft reporting name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportingNameCategory Context triple: [Farmer, reportingNameCategory, fighter aircraft reporting name]
-
A.
codeNameCategory
Indicates that an entity’s code name belongs to or is classified under a particular category of code names.
-
B.
isNameCategory
chosen
Indicates that something is classified as a particular category or type of name.
-
C.
canonicalCategory
Indicates that an entity is assigned to its primary or standard category within a classification system.
-
D.
nameElementCategory
Indicates that a given name or label belongs to, or is classified under, a particular element category.
-
E.
unitCategory
Indicates the classification or type of unit that an entity belongs to within a defined system or context.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:26 a.m.