Triple
T17598220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gallente Federation |
E428627
|
entity |
| Predicate | shipAesthetic |
P128167
|
FINISHED |
| Object | organic curves |
—
|
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: organic curves | Statement: [Gallente Federation, shipAesthetic, organic curves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipAesthetic Context triple: [Gallente Federation, shipAesthetic, organic curves]
-
A.
shipRepresents
Indicates that one entity (typically a ship) serves as a symbol, stand-in, or representation for another entity, concept, or group.
-
B.
shipDesigned
Indicates that one entity is responsible for designing or creating the design of a ship associated with another entity.
-
C.
shipFeatured
Indicates that a particular ship is highlighted or promoted as a featured item in a given context.
-
D.
shipsWith
Indicates that one entity is delivered, packaged, or provided together with another entity as part of the same shipment or bundle.
-
E.
shipDraft
Indicates the depth of a ship’s hull below the waterline, typically representing how deeply the vessel sits in the water.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469ecfb108190a9e7a5b380f8ab93 |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb50b448190a59dd4be33c76db7 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:51 a.m.