Triple
T21302698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pegasus Dwarf Spheroidal Galaxy |
E525108
|
entity |
| Predicate | isIrregular |
P27380
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Pegasus Dwarf Spheroidal Galaxy, isIrregular, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIrregular Context triple: [Pegasus Dwarf Spheroidal Galaxy, isIrregular, false]
-
A.
meetsIrregularly
Indicates that two or more entities come together or interact on a non-fixed, inconsistent, or unpredictable schedule.
-
B.
hasIrregularShape
chosen
Indicates that an entity possesses a form or outline that deviates from a regular, standard, or symmetrical shape.
-
C.
areRegularIn
Indicates that entities participate in or occur within a context, pattern, or structure in a consistent, uniform, and rule-governed manner.
-
D.
isRegular
Indicates that an entity consistently follows a defined pattern, rule, or schedule without significant deviation.
-
E.
isPer
Indicates that the subject entity is classified as a person.
- 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_69e0b517e6748190850d6f6ddf323d69 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7385da340819083c07f353f2142b0 |
completed | April 21, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:05 p.m.