Triple
T29138960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Covenant |
E738576
|
entity |
| Predicate | capitalShipClass |
P3141
|
FINISHED |
| Object | Assault Carrier |
—
|
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: Assault Carrier | Statement: [Covenant, capitalShipClass, Assault Carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalShipClass Context triple: [Covenant, capitalShipClass, Assault Carrier]
-
A.
isWarshipOf
Indicates that a given warship belongs to, is operated by, or is part of the naval forces of a specified country or organization.
-
B.
shipClass
chosen
Indicates the classification or type category to which a particular ship belongs.
-
C.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
D.
shipClassDeveloped
Indicates that a particular ship class was developed or designed by a specified entity (such as a country, organization, or manufacturer).
-
E.
BritishShipType
Indicates that the entity is classified as a type of ship associated with Britain, typically by origin, design, or service.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 28, 2026, 11:35 a.m.