Triple
T12316052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eight-Burst Nebula |
E293600
|
entity |
| Predicate | hasShapeDescription |
P11875
|
FINISHED |
| Object | figure-eight appearance in some images |
—
|
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: figure-eight appearance in some images | Statement: [Eight-Burst Nebula, hasShapeDescription, figure-eight appearance in some images]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShapeDescription Context triple: [Eight-Burst Nebula, hasShapeDescription, figure-eight appearance in some images]
-
A.
hasDescription
chosen
Indicates that an entity is associated with a textual description that explains or characterizes it.
-
B.
hasShapeModel
Indicates that an entity is associated with a specific geometric or structural shape model that represents its form.
-
C.
hasLowercaseShapeDescription
Indicates that the entity’s shape is described using a string consisting only of lowercase characters.
-
D.
hasUppercaseShapeDescription
Indicates that the description of a shape is written entirely in uppercase letters.
-
E.
hasShapeNickname
Indicates that an entity is associated with an informal or colloquial nickname referring to its shape.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.