Triple
T26529990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infrared Telescope (IRT) |
E670791
|
entity |
| Predicate | isGroundBased |
P134352
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Infrared Telescope (IRT), isGroundBased, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGroundBased Context triple: [Infrared Telescope (IRT), isGroundBased, false]
-
A.
usesGroundSystem
Indicates that one entity operates, relies on, or interacts with a particular ground-based system to perform its functions or services.
-
B.
isGroundedIn
Indicates that something is based on, supported by, or justified through a particular source, foundation, or set of principles.
-
C.
usesGroundFor
Indicates that one entity makes functional or practical use of a particular ground, surface, or land area for its activities or purposes.
-
D.
hasGroundPressure
Indicates that an entity exerts a specific amount of pressure on the ground or surface it is in contact with.
-
E.
isAerial
chosen
Indicates that one entity operates or exists in the air relative to another entity or context.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613f5ec28819099ec679f636d61d9 |
completed | May 2, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:34 a.m.