Triple
T29348355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaia (Asimov) |
E744233
|
entity |
| Predicate | proposedExtensionTo |
P54844
|
FINISHED |
| Object | entire Galaxy |
—
|
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: entire Galaxy | Statement: [Gaia (Asimov), proposedExtensionTo, entire Galaxy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedExtensionTo Context triple: [Gaia (Asimov), proposedExtensionTo, entire Galaxy]
-
A.
plannedExtensionTo
chosen
Indicates that one entity is intended or scheduled to be extended, expanded, or continued by another entity in the future.
-
B.
formerExtension
Indicates that one entity previously served as an extension or subsidiary part of another entity, but no longer holds that status.
-
C.
mayExtendTo
Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
-
D.
extension
Indicates that one entity is a lengthening, continuation, or added part of another entity beyond its original limits.
-
E.
wasExtendedTo
Indicates that something previously existing was lengthened, expanded, or prolonged to reach a new limit, scope, or duration.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 28, 2026, 2:04 p.m.