Triple
T21523163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geminids |
E531026
|
entity |
| Predicate | parentBodyAlternativeType |
P144700
|
FINISHED |
| Object | rock comet |
—
|
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: rock comet | Statement: [Geminids, parentBodyAlternativeType, rock comet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentBodyAlternativeType Context triple: [Geminids, parentBodyAlternativeType, rock comet]
-
A.
parentBodyType
Indicates that one entity has a body type that serves as the parent or base classification from which another entity's body type is derived or organized.
-
B.
associatedBody
Indicates a relationship where one entity is linked or connected to another entity as its related or corresponding body.
-
C.
publicBodyType
Indicates the classification or category of a public body (such as its organizational or legal type) within a governmental or public-sector context.
-
D.
representedBody
Indicates that one entity serves as a symbolic, artistic, or conceptual depiction of another entity’s body or physical form.
-
E.
primaryBodyType
Indicates the main physical form or category that characterizes an entity’s overall body structure or composition.
- 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee884db3ac81909e77d22d607ac72d |
completed | April 26, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:26 p.m.