Triple
T34752508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ticonderoga-class cruiser |
E1001819
|
entity |
| Predicate | earlyUnitsFeature |
P181815
|
FINISHED |
| Object | twin-arm missile launchers |
—
|
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: twin-arm missile launchers | Statement: [Ticonderoga-class cruiser, earlyUnitsFeature, twin-arm missile launchers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlyUnitsFeature Context triple: [Ticonderoga-class cruiser, earlyUnitsFeature, twin-arm missile launchers]
-
A.
earlyUse
Indicates that an entity is used or adopted at an unusually early time or stage relative to a typical or expected point of use.
-
B.
earlyVersion
Indicates that one entity is an earlier or preliminary version of another entity in a version sequence.
-
C.
earlyNetwork
Indicates that one entity is part of, or associated with, an initial or formative stage of a network in relation to another entity.
-
D.
earlyWar
Indicates that the war or conflict occurred in an early phase or at an earlier-than-typical point in a relevant timeline or sequence.
-
E.
earlyPhase
Indicates that the related process, project, or development is in its initial or beginning stage.
- 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_69f76db0fb30819096709d43f9a1f45f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: May 3, 2026, 3:59 p.m.