Triple
T9353262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairey Fulmar |
E225068
|
entity |
| Predicate | designedToMeet |
P9494
|
FINISHED |
| Object |
Specification O.8/38
Specification O.8/38 was a British Air Ministry requirement issued in the late 1930s for a carrier-based fighter aircraft that led to the development of the Fairey Fulmar.
|
E793250
|
NE FINISHED |
How this triple was built (4 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: Specification O.8/38 | Statement: [Fairey Fulmar, designedToMeet, Specification O.8/38]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Specification O.8/38 Context triple: [Fairey Fulmar, designedToMeet, Specification O.8/38]
-
A.
A-Spec
A-Spec is Acura’s sport-oriented trim and styling package that enhances select models with more aggressive design cues and performance-focused features.
-
B.
J80
J80 is the internal chassis code used by Toyota for the 80-series Land Cruiser platform that underpins the first-generation Lexus LX luxury SUV.
-
C.
Z84C00
The Z84C00 is the CMOS low-power, high-speed version of the classic Zilog Z80 8-bit microprocessor, widely used in embedded and legacy computing systems.
-
D.
B38M
B38M is the ICAO aircraft type designator for the Boeing 737 MAX 8 airliner.
-
E.
A388
A388 is the ICAO aircraft type designator for the Airbus A380, the world’s largest passenger airliner.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Specification O.8/38 Triple: [Fairey Fulmar, designedToMeet, Specification O.8/38]
Generated description
Specification O.8/38 was a British Air Ministry requirement issued in the late 1930s for a carrier-based fighter aircraft that led to the development of the Fairey Fulmar.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Specification O.8/38 Target entity description: Specification O.8/38 was a British Air Ministry requirement issued in the late 1930s for a carrier-based fighter aircraft that led to the development of the Fairey Fulmar.
-
A.
A-Spec
A-Spec is Acura’s sport-oriented trim and styling package that enhances select models with more aggressive design cues and performance-focused features.
-
B.
J80
J80 is the internal chassis code used by Toyota for the 80-series Land Cruiser platform that underpins the first-generation Lexus LX luxury SUV.
-
C.
Z84C00
The Z84C00 is the CMOS low-power, high-speed version of the classic Zilog Z80 8-bit microprocessor, widely used in embedded and legacy computing systems.
-
D.
B38M
B38M is the ICAO aircraft type designator for the Boeing 737 MAX 8 airliner.
-
E.
A388
A388 is the ICAO aircraft type designator for the Airbus A380, the world’s largest passenger airliner.
- F. None of above. chosen
Provenance (5 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_69ca842abfd48190949d71c3b86eeba8 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4f9515008190b01fbb43d673de2a |
completed | April 1, 2026, 5:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0e44f0a7881908b53a97715f4c6da |
completed | April 4, 2026, 10:13 a.m. |
| NEDg | Description generation | batch_69d0e5752a38819089b23ac52f0a6a39 |
completed | April 4, 2026, 10:18 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69d0e64cb4dc81908cef7d729d9cfb4d |
completed | April 4, 2026, 10:22 a.m. |
Created at: March 30, 2026, 7:41 p.m.