Triple
T23344716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 936 |
E591824
|
entity |
| Predicate | hasDiskAppearance |
P133181
|
FINISHED |
| Object | relatively featureless disk |
—
|
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: relatively featureless disk | Statement: [NGC 936, hasDiskAppearance, relatively featureless disk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiskAppearance Context triple: [NGC 936, hasDiskAppearance, relatively featureless disk]
-
A.
supportsDiskDrives
Indicates that one entity is capable of accommodating, operating, or being compatible with disk drives associated with another entity.
-
B.
hasTypicalAppearance
chosen
Indicates that an entity exhibits the standard or commonly expected visual form or look associated with its kind.
-
C.
hasMediaAppearanceIn
Indicates that an entity appears or is featured as media content within a specified media work, program, or publication.
-
D.
hasNuclearDisk
Indicates that an entity possesses a distinct, disk-shaped structure composed of material concentrated in its central or nuclear region.
-
E.
hasInternalHardDrive
Indicates that one entity possesses an internal hard drive as a built-in storage component.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f198358fb8819094c74cfd53cbab44 |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:19 p.m.