Triple
T21410126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 23850 |
E528144
|
entity |
| Predicate | clusterCoreMember |
P20032
|
FINISHED |
| Object | no, located toward cluster outskirts |
—
|
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: no, located toward cluster outskirts | Statement: [HD 23850, clusterCoreMember, no, located toward cluster outskirts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clusterCoreMember Context triple: [HD 23850, clusterCoreMember, no, located toward cluster outskirts]
-
A.
hasCoreMember
chosen
Indicates that an entity includes another entity as a central or primary member of its group, organization, or structure.
-
B.
isNearestProminentClusterMemberOf
Indicates that an entity is the closest significant member within a cluster relative to another specified entity or reference point.
-
C.
hostCluster
Indicates a relationship where one cluster serves as the hosting or parent environment for another resource, service, or sub-cluster.
-
D.
committeeMember
Indicates that an entity serves as a member of a particular committee.
-
E.
FCSMember
Indicates that an entity is a member of, or affiliated with, the FCS (e.g., a specific conference, system, or organizational group).
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b1b4d4608190a86a6cd279709b21 |
completed | April 22, 2026, 11:32 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:41 p.m.