Triple
T28880708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GW170814 |
E732408
|
entity |
| Predicate | hasSkyLocalizationImprovementFactor |
P166249
|
FINISHED |
| Object | about 10 |
—
|
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: about 10 | Statement: [GW170814, hasSkyLocalizationImprovementFactor, about 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSkyLocalizationImprovementFactor Context triple: [GW170814, hasSkyLocalizationImprovementFactor, about 10]
-
A.
hasSatelliteLocation
Indicates that an entity has a secondary or remote location associated with it, such as a branch, satellite office, or auxiliary site.
-
B.
locatedInSkyRegion
Indicates that an entity is situated within or associated with a specific region or area of the sky.
-
C.
hasSelenographicCoordinateSystem
Indicates that something is associated with or defined using a coordinate system based on the Moon’s (selenographic) latitude and longitude.
-
D.
hasSkyType
Indicates that something possesses or is associated with a particular type or classification of sky.
-
E.
hasSkyColor
Indicates that an entity’s sky is characterized by a particular color.
- F. None of above. chosen
Provenance (4 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_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 7:43 a.m.