Triple
T21523195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geminids |
E531026
|
entity |
| Predicate | parentBodyDiscovery |
P144706
|
FINISHED |
| Object | 3200 Phaethon discovered in 1983 |
—
|
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: 3200 Phaethon discovered in 1983 | Statement: [Geminids, parentBodyDiscovery, 3200 Phaethon discovered in 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentBodyDiscovery Context triple: [Geminids, parentBodyDiscovery, 3200 Phaethon discovered in 1983]
-
A.
hasBodyDiscoveryLocation
Indicates the location where a body was found or discovered.
-
B.
discoveredOnBodyBy
Indicates that a body was discovered by a particular person or agent.
-
C.
discoveredOnBody
Indicates that something (such as an item, mark, or substance) was found on the surface or person of a body.
-
D.
hasParentBodyHypothesis
Indicates that one hypothesis is associated with or derived from a broader, encompassing parent hypothesis.
-
E.
bodyPositionAtDiscovery
Indicates the physical position or posture in which a body was found at the time of its discovery.
- 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.