Triple
T18772256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BD+30 540 |
E459043
|
entity |
| Predicate | isNearbyAssociationMember |
P18252
|
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: [BD+30 540, isNearbyAssociationMember, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNearbyAssociationMember Context triple: [BD+30 540, isNearbyAssociationMember, true]
-
A.
hasNearbyAccess
Indicates that one entity has convenient, close-proximity access to another resource, service, or location.
-
B.
hasNearbyDiscovery
Indicates that one entity has a discovery located in close physical or spatial proximity to it.
-
C.
hasNearbyPass
Indicates that an entity has at least one pass (e.g., transit or access pass) available within a short or locally defined distance from it.
-
D.
hasNearbyMode
chosen
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
-
E.
isNearestProminentClusterMemberOf
Indicates that an entity is the closest significant member within a cluster relative to another specified entity or reference point.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59336a6b08190819595a55177264e |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.