Triple
T33710639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cruiser Division 18 |
E863725
|
entity |
| Predicate | shipTypeAssigned |
P8971
|
FINISHED |
| Object | heavy cruiser |
—
|
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: heavy cruiser | Statement: [Cruiser Division 18, shipTypeAssigned, heavy cruiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipTypeAssigned Context triple: [Cruiser Division 18, shipTypeAssigned, heavy cruiser]
-
A.
shipAssignment
Indicates the association between a ship and the specific task, route, or entity it has been assigned to.
-
B.
shipManager
Indicates a relationship where one entity manages, oversees, or is responsible for the operation and administration of a ship.
-
C.
shipTypeInvolved
chosen
Indicates that a particular type or class of ship is involved or participates in a specified event, situation, or relationship.
-
D.
shipTypeFavored
Indicates that a particular type of ship is preferred or favored over others in a given context.
-
E.
shipAssociatedWith
Indicates that there is a relevant connection or involvement between a ship and another entity, such as ownership, operation, registration, or functional association.
- 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_69f3498844608190bb8f9b14908d2510 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fabac0a08190aae0129f93f0b23e |
completed | May 3, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:43 a.m.