Triple
T18443913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R Coronae Australis |
E450604
|
entity |
| Predicate | hasNearbyObjects |
P118122
|
FINISHED |
| Object | other young stellar objects in Corona Australis |
—
|
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: other young stellar objects in Corona Australis | Statement: [R Coronae Australis, hasNearbyObjects, other young stellar objects in Corona Australis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyObjects Context triple: [R Coronae Australis, hasNearbyObjects, other young stellar objects in Corona Australis]
-
A.
hasNotableNearbyEntity
Indicates that one entity has another significant or noteworthy entity located in its close physical or contextual proximity.
-
B.
hasNearbyFunction
Indicates that one entity has another entity located close by that serves a related or supportive function.
-
C.
hasMaterialNearby
Indicates that one entity has a material located in its immediate vicinity or surrounding area.
-
D.
hasNearbyPoint
chosen
Indicates that one entity has at least one other point located within a specified proximity or distance from it.
-
E.
hasNearbyDiscovery
Indicates that one entity has a discovery located in close physical or spatial proximity to it.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c142abc8190b4f6f938acdc413d |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:30 a.m.