Triple
T27535174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electromagnetic Aircraft Launch System |
E695076
|
entity |
| Predicate | usedOnClass |
P108592
|
FINISHED |
| Object | Ford-class aircraft carrier |
—
|
NE NERFINISHED |
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: Ford-class aircraft carrier | Statement: [Electromagnetic Aircraft Launch System, usedOnClass, Ford-class aircraft carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnClass Context triple: [Electromagnetic Aircraft Launch System, usedOnClass, Ford-class aircraft carrier]
-
A.
usedByClass
chosen
Indicates that something (such as a resource, method, or component) is utilized or depended upon by a particular class.
-
B.
usesClass
Indicates that one entity makes use of, depends on, or is implemented using a particular class in its structure or behavior.
-
C.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
D.
usedOnPart
Indicates that something is applied to, operates on, or is intended for use with a specific part of a larger object or system.
-
E.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f5996508190894a769a5199945d |
completed | May 2, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69f623ac3a9c8190a6ee0c137b09e4b0 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:28 p.m.