Triple
T34752505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ticonderoga-class cruiser |
E1001819
|
entity |
| Predicate | hullNumberPrefix |
P181573
|
FINISHED |
| Object | CG |
—
|
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: CG | Statement: [Ticonderoga-class cruiser, hullNumberPrefix, CG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hullNumberPrefix Context triple: [Ticonderoga-class cruiser, hullNumberPrefix, CG]
-
A.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
B.
hullNumberRange
Indicates a relationship where an entity’s hull number falls within a specified numeric range.
-
C.
sailNumberPrefix
Indicates that one entity is the prefix portion of the identifying sail number assigned to another entity (typically a boat or sailing vessel).
-
D.
hullNumberInRussianService
Indicates that an entity has a specific hull identification number assigned to it while in Russian naval service.
-
E.
hullNumberInIndianService
Indicates that a specific hull number is the one assigned to a vessel while it is in service with the Indian armed forces or maritime authorities.
- 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_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f77ff804f08190b431a31e6179ace4 |
completed | May 3, 2026, 5:03 p.m. |
Created at: May 3, 2026, 3:59 p.m.