Triple
T23527719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAO 98167 |
E576477
|
entity |
| Predicate | isMemberOfBeehiveCluster |
P96993
|
FINISHED |
| Object | no |
—
|
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 | Statement: [SAO 98167, isMemberOfBeehiveCluster, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMemberOfBeehiveCluster Context triple: [SAO 98167, isMemberOfBeehiveCluster, no]
-
A.
isClusteredFormation
Indicates that multiple entities are arranged or grouped closely together in a compact formation.
-
B.
hasCluster
chosen
Indicates that one entity possesses, contains, or is associated with a specific cluster or grouping of related elements.
-
C.
isNearestProminentClusterMemberOf
Indicates that an entity is the closest significant member within a cluster relative to another specified entity or reference point.
-
D.
hasITCluster
Indicates that an entity possesses, hosts, or is associated with a specific information technology (IT) cluster.
-
E.
hasPrimaryClusterIn
Indicates that an entity’s main or most significant cluster is located within or associated with a specified cluster or grouping.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac74be1881909161b94aa611188a |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:09 p.m.