Triple
T36254619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irregular satellites |
E891897
|
entity |
| Predicate | oftenBelongTo |
P109249
|
FINISHED |
| Object | collisional families |
—
|
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: collisional families | Statement: [Irregular satellites, oftenBelongTo, collisional families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenBelongTo Context triple: [Irregular satellites, oftenBelongTo, collisional families]
-
A.
believedToBelongTo
Indicates that something is thought or assumed, but not definitively known, to be owned by or part of a particular entity.
-
B.
canBelongTo
Indicates that something is capable of being a member or part of a particular group, category, or owner.
-
C.
oftenPartOf
chosen
Indicates that one entity frequently occurs as a component or subset within another entity, though not necessarily always.
-
D.
proposedToBelongTo
Indicates that one entity has been suggested or put forward as potentially belonging to, or being a member/part of, another entity or group.
-
E.
oftenRefersTo
Indicates that one entity is frequently used to mention, denote, or reference another entity in common usage or context.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: May 3, 2026, 4:09 p.m.