Triple
T4618804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | observable universe |
E100929
|
entity |
| Predicate | hasExpansionDescription |
P57010
|
FINISHED |
| Object | space within it is expanding |
—
|
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: space within it is expanding | Statement: [observable universe, hasExpansionDescription, space within it is expanding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpansionDescription Context triple: [observable universe, hasExpansionDescription, space within it is expanding]
-
A.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
B.
hasExpansionType
Indicates that an entity is associated with a particular mode or category of expansion (such as how it grows, extends, or scales).
-
C.
expansionStatus
Indicates the current state or phase of growth, enlargement, or extension of something relative to its previous or intended size or scope.
-
D.
expandedBy
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
-
E.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e247448190ad92f194cb1127c5 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd556b93cc8190ab817d2817109a0b |
completed | March 20, 2026, 2:10 p.m. |
Created at: March 20, 2026, 1:12 p.m.