Triple
T20446833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tucana II |
E501537
|
entity |
| Predicate | hasImportanceIn |
P81001
|
FINISHED |
| Object | near-field cosmology |
—
|
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: near-field cosmology | Statement: [Tucana II, hasImportanceIn, near-field cosmology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImportanceIn Context triple: [Tucana II, hasImportanceIn, near-field cosmology]
-
A.
isImportantFor
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
B.
resultImportance
Indicates that one entity specifies how significant, critical, or impactful the outcome or result of another entity is.
-
C.
hasJurisdictionalImportance
Indicates that something holds significant relevance or influence within a particular legal or administrative jurisdiction.
-
D.
hasResearchImportance
chosen
Indicates that something holds significance or value within a research context, such as contributing meaningfully to scientific or scholarly investigation.
-
E.
peakImportance
Indicates that something reaches or represents the highest level of importance within a given context or timeframe.
- 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_69e0b4ac0a1c81908845d0f8a56abce8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e68cfe57a8819094bd3d324bd567f5 |
completed | April 20, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:32 a.m.