Triple
T5561186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrokoth |
E145768
|
entity |
| Predicate | formationScenario |
P55686
|
FINISHED |
| Object | gentle merger of two primordial bodies |
—
|
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: gentle merger of two primordial bodies | Statement: [Arrokoth, formationScenario, gentle merger of two primordial bodies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formationScenario Context triple: [Arrokoth, formationScenario, gentle merger of two primordial bodies]
-
A.
scenarioType
chosen
Indicates the specific category or kind of situation, context, or use case that an entity or event is associated with.
-
B.
formationType
Indicates the specific structural or organizational configuration in which something is arranged, created, or formed.
-
C.
onFormation
Indicates that one entity is located on or attached to the surface of a formation (such as a geological or structural feature).
-
D.
formationMechanism
Indicates the process or mechanism by which something is formed, created, or brought into existence.
-
E.
controlledFormation
Indicates that one entity intentionally directs, regulates, or governs the way another entity comes into existence or is formed.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0201857848190a5443b51bcdb63fa |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.