Triple
T32212844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3D-HST survey |
E822853
|
entity |
| Predicate | observesPopulation |
P130315
|
FINISHED |
| Object | distant galaxies |
—
|
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: distant galaxies | Statement: [3D-HST survey, observesPopulation, distant galaxies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observesPopulation Context triple: [3D-HST survey, observesPopulation, distant galaxies]
-
A.
monitoredPopulation
chosen
Indicates that a given group or population is being systematically observed, tracked, or measured by another entity.
-
B.
viewOnPopulation
Indicates a stance, opinion, or perspective that an entity holds regarding population size, growth, or related demographic issues.
-
C.
populationScale
Indicates the relative size or magnitude of a population, typically categorizing it into broad scale levels (e.g., small, medium, large).
-
D.
populationState
Indicates the condition or status of a population at a given point in time, such as its size, distribution, or demographic characteristics.
-
E.
plannedPopulation
Indicates the intended or projected number of individuals expected to occupy or use something, such as a facility, area, or system, according to a plan.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 12:37 a.m.