Triple
T34982055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trabe |
E1008840
|
entity |
| Predicate | shipTechnology |
P182165
|
FINISHED |
| Object | advanced starships |
—
|
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: advanced starships | Statement: [Trabe, shipTechnology, advanced starships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipTechnology Context triple: [Trabe, shipTechnology, advanced starships]
-
A.
navalTechnologyType
Indicates the specific category or type of naval technology associated with an entity.
-
B.
marineStrength
Indicates the degree of power, capability, or effectiveness associated with a marine or naval force in a given context.
-
C.
navalFeatures
Indicates that something possesses characteristics, components, or attributes specifically associated with naval or maritime contexts.
-
D.
shipDesigned
Indicates that one entity is responsible for designing or creating the design of a ship associated with another entity.
-
E.
shipClass
Indicates the classification or type category to which a particular ship belongs.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7870dfe108190996c0c68630edc7f |
completed | May 3, 2026, 5:34 p.m. |
Created at: May 3, 2026, 4:01 p.m.