Triple
T19686272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Butterfly Cluster |
E472718
|
entity |
| Predicate | notableShape |
P61000
|
FINISHED |
| Object | butterfly-like pattern |
—
|
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: butterfly-like pattern | Statement: [Butterfly Cluster, notableShape, butterfly-like pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableShape Context triple: [Butterfly Cluster, notableShape, butterfly-like pattern]
-
A.
notableSurface
Indicates that one entity is a surface or exterior of particular significance or prominence in relation to another entity.
-
B.
notableFeatureOn
chosen
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
C.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
notableCorner
Indicates that a specific corner or intersection is distinguished or significant in some notable way within a given context.
-
E.
notableDecoration
Indicates that an entity has received a particular honor, award, or decoration that is considered especially significant or distinguished.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6420c3f50819082b64b1fa4335e56 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.