Triple
T2251725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimitz-class aircraft carrier |
E49631
|
entity |
| Predicate | shipBeam |
P36728
|
FINISHED |
| Object | about 77 meters (flight deck) |
—
|
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: about 77 meters (flight deck) | Statement: [Nimitz-class aircraft carrier, shipBeam, about 77 meters (flight deck)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipBeam Context triple: [Nimitz-class aircraft carrier, shipBeam, about 77 meters (flight deck)]
-
A.
shipUsed
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
-
B.
beam
Indicates that one entity emits, directs, or projects a concentrated line or stream (such as light, energy, or information) toward another entity.
-
C.
shipAssignment
Indicates the association between a ship and the specific task, route, or entity it has been assigned to.
-
D.
shipSponsor
Indicates that one entity serves as the sponsor or patron responsible for supporting, endorsing, or funding a particular ship.
-
E.
shipsWith
Indicates that one entity is delivered, packaged, or provided together with another entity as part of the same shipment or bundle.
- 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc11d04688190abc04fac3a1804a9 |
completed | March 7, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe86dbcc81908c72793af8fe2a4d |
completed | March 7, 2026, 5:58 a.m. |
Created at: March 4, 2026, 7:47 p.m.