Triple
T1816944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F/A-18 Hornet |
E40455
|
entity |
| Predicate | crewNote |
P32618
|
FINISHED |
| Object | single-seat and two-seat variants |
—
|
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 and two-seat variants | Statement: [F/A-18 Hornet, crewNote, single-seat and two-seat variants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewNote Context triple: [F/A-18 Hornet, crewNote, single-seat and two-seat variants]
-
A.
navigationNote
Indicates that there is an auxiliary note or instruction intended to guide or assist navigation within a resource, interface, or environment.
-
B.
isNotedOn
Indicates that information about one entity is recorded, mentioned, or annotated on another entity (such as a document, record, or medium).
-
C.
crewModule
Indicates that an object functions as or contains a crew module, i.e., a section designed to house and support crew members.
-
D.
crewOutcome
Indicates the result or status experienced by a crew as a consequence of an event, action, or condition.
-
E.
notedIn
Indicates that information about one entity is mentioned, recorded, or referenced within another entity, such as a document, record, or source.
- 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_69a8864526c081908a3a4d74f689e2c5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aba67721788190951beae25e885457 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61d884548190a19cf3a6b5ae9d48 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69aba67554788190b429f2b9f0a70310 |
completed | March 7, 2026, 4:15 a.m. |
Created at: March 4, 2026, 7:32 p.m.