Triple
T34985991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sovereign-class |
E1008947
|
entity |
| Predicate | designerRealWorld |
P12117
|
FINISHED |
| Object | John Eaves |
—
|
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: John Eaves | Statement: [Sovereign-class, designerRealWorld, John Eaves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designerRealWorld Context triple: [Sovereign-class, designerRealWorld, John Eaves]
-
A.
designerType
Indicates the specific kind or category of designer role associated with an entity.
-
B.
designerAlias
Indicates that one name or label is used as an alternative alias for a designer.
-
C.
designersInUniverse
Indicates that certain designers exist or are present within a specified universe or conceptual domain.
-
D.
designerOccupation
chosen
Indicates that one entity serves as the professional designer or design specialist for another entity.
-
E.
worldDesign
Indicates the relationship by which an entity is responsible for creating, shaping, or specifying the structure, rules, and features of a fictional or virtual world.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: May 3, 2026, 4:01 p.m.