Triple
T5202257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milky Way stellar halo |
E117419
|
entity |
| Predicate | outerExtent |
P22930
|
FINISHED |
| Object | ≈ 100 kiloparsecs or more |
—
|
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: ≈ 100 kiloparsecs or more | Statement: [Milky Way stellar halo, outerExtent, ≈ 100 kiloparsecs or more]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outerExtent Context triple: [Milky Way stellar halo, outerExtent, ≈ 100 kiloparsecs or more]
-
A.
maximumExtent
chosen
Indicates the greatest or furthest degree, size, or range to which something can extend or apply within a given context.
-
B.
currentExtentDesignated
Indicates that the currently applicable spatial or conceptual extent of something has been formally defined or designated.
-
C.
eezExtent
Indicates the geographic area or spatial coverage of a country's exclusive economic zone (EEZ).
-
D.
externalDimension
Indicates that an entity has a measurable size or extent along one or more outer spatial dimensions (such as length, width, or height).
-
E.
territorialExtent
Indicates the geographic area or spatial range over which something extends, applies, or has jurisdiction.
- 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_69bd4463dd3c81909966123f20b79d57 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adb034c819086bf8a85fbf158f4 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77b9a67c8190819612257ea746b4 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.