Triple
T14286144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bachelor and Three Graces |
E354180
|
entity |
| Predicate | isClusteredFormation |
P113613
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bachelor and Three Graces, isClusteredFormation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClusteredFormation Context triple: [Bachelor and Three Graces, isClusteredFormation, true]
-
A.
hasCluster
Indicates that one entity possesses, contains, or is associated with a specific cluster or grouping of related elements.
-
B.
isRichCluster
Indicates that a given cluster possesses the properties and characteristics of a rich cluster (e.g., high galaxy density and mass).
-
C.
isOldCluster
Indicates that a given cluster has existed for a long time or has reached an advanced age relative to other clusters.
-
D.
containsFormation
Indicates that one entity spatially or structurally includes or encloses a formation as part of its extent or composition.
-
E.
isMassiveCluster
Indicates that an entity forms or belongs to a very large, densely grouped collection of related entities.
- F. None of above. chosen
Provenance (4 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de697ef40c8190bea37724b28c2e99 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:11 a.m.