Triple
T18257614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble constant |
E437255
|
entity |
| Predicate | hasAssociatedTension |
P11899
|
FINISHED |
| Object | Hubble tension |
—
|
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: Hubble tension | Statement: [Hubble constant, hasAssociatedTension, Hubble tension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedTension Context triple: [Hubble constant, hasAssociatedTension, Hubble tension]
-
A.
hasTension
Indicates the presence of strain, stress, or conflict between entities in their relationship or interaction.
-
B.
tension
chosen
Indicates a state of strain, stress, or conflict existing between entities, often involving opposing forces, interests, or emotions.
-
C.
tensionArea
Indicates the region or extent over which mechanical or emotional tension is distributed or experienced.
-
D.
hasCoupling
Indicates that two entities are linked or joined together in a way that allows them to interact, transfer, or coordinate motion, energy, or information.
-
E.
hasStrongTiesTo
Indicates a close, influential, and enduring relationship or connection exists between the referenced entities.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd86e21081909c049082949b95c6 |
completed | April 19, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.