Triple
T18695486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taurus molecular cloud complex |
E457104
|
entity |
| Predicate | hasLinearSize |
P34032
|
FINISHED |
| Object | about 30 parsecs |
—
|
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: about 30 parsecs | Statement: [Taurus molecular cloud complex, hasLinearSize, about 30 parsecs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLinearSize Context triple: [Taurus molecular cloud complex, hasLinearSize, about 30 parsecs]
-
A.
hasSize
chosen
Indicates that one entity possesses a particular physical magnitude or extent, such as length, volume, or overall dimensions.
-
B.
hasMatrixSize
Indicates that an entity (such as a matrix or array) has a specific dimensional size, typically expressed as its number of rows and columns.
-
C.
hasRelativeSize
Indicates that one entity’s size is being compared to another entity’s size, expressing a relative rather than absolute magnitude.
-
D.
hasDimension
Indicates that an entity possesses a specific measurable extent or size along one or more axes (e.g., length, width, height).
-
E.
hasMinimumSize
Indicates that an entity meets or exceeds a specified minimum size threshold.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e775408190996b4c613b83f185 |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.