Triple
T35691369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Veers |
E1031299
|
entity |
| Predicate | hasLegendsMaterial |
P196438
|
FINISHED |
| Object | Star Wars Legends expanded universe |
—
|
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: Star Wars Legends expanded universe | Statement: [General Veers, hasLegendsMaterial, Star Wars Legends expanded universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegendsMaterial Context triple: [General Veers, hasLegendsMaterial, Star Wars Legends expanded universe]
-
A.
isLegendaryForSet
Indicates that an entity is classified as a legendary item specifically within the context of a given set or collection.
-
B.
isLegendaryStatus
Indicates that an entity possesses a legendary status, typically signifying exceptional rarity, renown, or significance within a given context.
-
C.
hasCultOrLegend
Indicates that an entity is associated with, or is the subject of, a cult, myth, or legendary tradition.
-
D.
hasLanternMaterial
Indicates that an entity’s lantern is made from or composed of a specified material.
-
E.
hasSpireMaterial
Indicates that the material composition of a spire is a specified substance or material.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
| PDg | Predicate description generation | batch_69fe349739cc8190a21c408208312e6c |
completed | May 8, 2026, 7:08 p.m. |
Created at: May 3, 2026, 4:05 p.m.