Triple
T19261539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abell 3526 |
E481659
|
entity |
| Predicate | isNearbyCluster |
P61362
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Abell 3526, isNearbyCluster, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNearbyCluster Context triple: [Abell 3526, isNearbyCluster, yes]
-
A.
isNearestProminentClusterMemberOf
Indicates that an entity is the closest significant member within a cluster relative to another specified entity or reference point.
-
B.
hasNearbyHotelCluster
Indicates that one or more hotels are located in close proximity to the referenced place or area, forming a spatial cluster.
-
C.
hasNearbyPoint
Indicates that one entity has at least one other point located within a specified proximity or distance from it.
-
D.
hasNearbyFunction
Indicates that one entity has another entity located close by that serves a related or supportive function.
-
E.
nearbyTo
chosen
Indicates that one entity is located close in distance or position to another entity.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8a022c8190b313e9d11d38e482 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.