Triple
T34795671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LCOGT telescopes |
E1003072
|
entity |
| Predicate | isGlobalNetwork |
P171231
|
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: [LCOGT telescopes, isGlobalNetwork, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGlobalNetwork Context triple: [LCOGT telescopes, isGlobalNetwork, true]
-
A.
hasGlobalNetworkType
Indicates that an entity is associated with a specific type or category of global network.
-
B.
isNetworkOf
chosen
Indicates that one entity functions as a network that connects, supports, or encompasses another entity or set of entities.
-
C.
hasGlobalDistribution
Indicates that the related entity occurs, operates, or is present across most or all regions of the world rather than being confined to a specific locality or region.
-
D.
canBeGlobal
Indicates that something has the potential or permission to apply, operate, or be recognized at a global scope rather than a local or limited one.
-
E.
hasGlobalRegion
Indicates that an entity is associated with or belongs to a specific global geographic region.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77a84e7a481908e7654a6ea31968e |
completed | May 3, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.