Triple
T18067301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halley’s Comet of 1066 |
E432324
|
entity |
| Predicate | hasCometType |
P16808
|
FINISHED |
| Object | short-period comet appearance |
—
|
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: short-period comet appearance | Statement: [Halley’s Comet of 1066, hasCometType, short-period comet appearance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCometType Context triple: [Halley’s Comet of 1066, hasCometType, short-period comet appearance]
-
A.
hasCompositionType
Indicates that one entity is composed of or formed by another entity in a specific structural or material way.
-
B.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
hasJetType
Indicates that an entity is associated with or characterized by a specific type or category of jet.
-
D.
hasCurrentType
Indicates that an entity currently possesses or is classified under a specific type or category, as opposed to past or potential types.
-
E.
hasConeType
Indicates that an entity possesses or is associated with a specific type or category of cone.
- 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4cceb020081909329492591e7b1f2 |
completed | April 19, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:26 a.m.