Triple
T28880698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GW170814 |
E732408
|
entity |
| Predicate | hasLuminosityDistance |
P66671
|
FINISHED |
| Object | 540 million 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: 540 million parsecs | Statement: [GW170814, hasLuminosityDistance, 540 million parsecs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLuminosityDistance Context triple: [GW170814, hasLuminosityDistance, 540 million parsecs]
-
A.
hasDistanceModulus
Indicates a relationship where a specific distance modulus value is associated with the separation between two entities or locations.
-
B.
hasLuminosityFunction
Indicates that there is an associated luminosity function characterizing how brightness or light output is distributed for the given entity or system.
-
C.
hasApproximateDistanceFromEarth
chosen
Indicates that there is an estimated or non-exact distance between an entity and Earth.
-
D.
hasLuminosityOfPrimary
Indicates that one entity has the same luminosity value or luminosity classification as the primary entity in a given system or context.
-
E.
hasLumen
Indicates that one entity possesses or is characterized by a specific luminous intensity or light output measured in lumens.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a6d639481909e661755a5838a47 |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:43 a.m.