Triple
T18443880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 6726 |
E450603
|
entity |
| Predicate | apparentInstruments |
P131633
|
FINISHED |
| Object | small telescopes |
—
|
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: small telescopes | Statement: [NGC 6726, apparentInstruments, small telescopes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apparentInstruments Context triple: [NGC 6726, apparentInstruments, small telescopes]
-
A.
includesInstruments
Indicates that one entity contains, involves, or makes use of one or more instruments as part of its composition or execution.
-
B.
instruments
Indicates that an agent uses a tool, device, or means to carry out an action or achieve an effect.
-
C.
usedAsInstrumentBy
Indicates that one entity functions as a tool, means, or instrument through which another entity performs an action or achieves an effect.
-
D.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
E.
numberOfInstruments
Indicates the quantitative count of instruments associated with or involved in a given entity or event.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:30 a.m.