Triple
T37212481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 6207 |
E922643
|
entity |
| Predicate | hasNearbyObjectInField |
P132906
|
FINISHED |
| Object | globular cluster M13 |
—
|
NE NERFINISHED |
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: globular cluster M13 | Statement: [NGC 6207, hasNearbyObjectInField, globular cluster M13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyObjectInField Context triple: [NGC 6207, hasNearbyObjectInField, globular cluster M13]
-
A.
hasNeighboringObject
chosen
Indicates that one object is located adjacent to or directly next to another object in space.
-
B.
hasNotableNearbyEntity
Indicates that one entity has another significant or noteworthy entity located in its close physical or contextual proximity.
-
C.
hasNearbyEntityType
Indicates that an entity has at least one other entity of a specified type located within a defined nearby spatial or contextual range.
-
D.
hasNearbyFunction
Indicates that one entity has another entity located close by that serves a related or supportive function.
-
E.
hasMaterialNearby
Indicates that one entity has a material located in its immediate vicinity or surrounding area.
- 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a008d6085508190a71c52cd028a6297 |
completed | May 10, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a008ced31448190b8fc60bf87b40647 |
completed | May 10, 2026, 1:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.