Triple
T6301609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Cancri |
E141267
|
entity |
| Predicate | isUsedAsReferencePointFor |
P11053
|
FINISHED |
| Object | locating the Beehive Cluster |
—
|
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: locating the Beehive Cluster | Statement: [Delta Cancri, isUsedAsReferencePointFor, locating the Beehive Cluster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedAsReferencePointFor Context triple: [Delta Cancri, isUsedAsReferencePointFor, locating the Beehive Cluster]
-
A.
isReferencePointFor
chosen
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
-
B.
isStartingPointOf
Indicates that something serves as the initial point or origin from which another thing, process, or path begins.
-
C.
isReferencedIn
Indicates that one entity is cited, mentioned, or otherwise referred to within another entity.
-
D.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
E.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
- 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_69c008cf0ad4819095def81e2bd42f9f |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0645bb41481909294b06e2b3e1845 |
completed | March 22, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:27 p.m.