Triple
T30639928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agent to the Stars |
E779944
|
entity |
| Predicate | hasAlienDescription |
P11875
|
FINISHED |
| Object | Aliens are gelatinous and emit a strong odor. |
—
|
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: Aliens are gelatinous and emit a strong odor. | Statement: [Agent to the Stars, hasAlienDescription, Aliens are gelatinous and emit a strong odor.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlienDescription Context triple: [Agent to the Stars, hasAlienDescription, Aliens are gelatinous and emit a strong odor.]
-
A.
hasAlienSpecies
Indicates that one entity possesses, contains, or is associated with a particular alien species.
-
B.
featuresAlien
Indicates that something includes, presents, or prominently involves an alien or extraterrestrial being.
-
C.
hasAlienCharacters
Indicates that an entity includes or features characters that are extraterrestrial or non-human in origin.
-
D.
hasDescription
chosen
Indicates that an entity is associated with a textual description that explains or characterizes it.
-
E.
mainAlienCharacter
Indicates that the referenced entity serves as the primary alien character in a narrative or work.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 29, 2026, 8:29 p.m.