Triple
T3345199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwarzschild crater |
E70356
|
entity |
| Predicate | hasColongitude |
P34243
|
FINISHED |
| Object | ~186 |
—
|
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: ~186 | Statement: [Schwarzschild crater, hasColongitude, ~186]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColongitude Context triple: [Schwarzschild crater, hasColongitude, ~186]
-
A.
colongitude
chosen
Indicates the angular distance of a point (typically on a rotating body) measured westward from a defined prime meridian, often used to specify its position relative to the body’s rotation or illumination.
-
B.
hasTropicOfCancerCrossing
Indicates that the specified entity is geographically intersected or crossed by the Tropic of Cancer.
-
C.
coordinateLongitude
Indicates the east–west geographic position of an entity on the Earth’s surface, expressed as a longitude value.
-
D.
parallelOfLatitude
Indicates that one entity is a line or circle on a sphere (typically Earth) that is at a constant latitude relative to another reference.
-
E.
meetsAtPolesWith
Indicates that two entities intersect or come into contact specifically at their polar regions or endpoints.
- 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1f36c74819093ef2c74a46c2351 |
completed | March 8, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.