Triple
T27743617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halley’s Comet |
E701919
|
entity |
| Predicate | hasNucleusDimensions |
P182747
|
FINISHED |
| Object | approximately 15 km × 8 km × 8 km |
—
|
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: approximately 15 km × 8 km × 8 km | Statement: [Halley’s Comet, hasNucleusDimensions, approximately 15 km × 8 km × 8 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNucleusDimensions Context triple: [Halley’s Comet, hasNucleusDimensions, approximately 15 km × 8 km × 8 km]
-
A.
hasNucleusShape
Indicates that an entity possesses a nucleus with a specific geometric or morphological shape.
-
B.
isNucleusOf
Indicates that one entity functions as the central or most important core component of another entity.
-
C.
hasNucleusActivity
Indicates that an entity performs, exhibits, or is involved in functional activity occurring within a nucleus.
-
D.
hasActiveNucleus
Indicates that the referenced entity possesses a nucleus that is currently functioning or exhibiting biological activity.
-
E.
hasNuclearRegion
Indicates that an entity possesses or includes a specific nuclear region as a distinct part or component.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7908ec35881909a42f954fb9fa16e |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78fd3fd888190b7db0b563f298585 |
completed | May 3, 2026, 6:11 p.m. |
Created at: April 27, 2026, 4:13 p.m.