Triple
T36254606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irregular satellites |
E891897
|
entity |
| Predicate | areFoundAround |
P164553
|
FINISHED |
| Object | Jupiter |
—
|
NE NERFINISHED |
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: Jupiter | Statement: [Irregular satellites, areFoundAround, Jupiter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areFoundAround Context triple: [Irregular satellites, areFoundAround, Jupiter]
-
A.
isOftenLocatedAround
chosen
Indicates that one entity is frequently found in the vicinity of, or surrounding, another entity.
-
B.
isCommonlyFoundAt
Indicates that an entity typically or frequently occurs, appears, or is present in a particular location or context.
-
C.
around
Indicates that one entity is located or moves on all or most sides of another entity, encircling or surrounding it spatially.
-
D.
commonlyFoundOn
Indicates that one entity is typically or frequently located on, attached to, or present upon another entity.
-
E.
formsAround
Indicates that one entity develops or shapes itself so as to encircle, surround, or be organized around another entity.
- 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_69f7b5fd3f8481908b9380f82a2310f0 |
completed | May 3, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.