Triple
T25638017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adrastea |
E642758
|
entity |
| Predicate | helpsSupplyMaterialTo |
P22211
|
FINISHED |
| Object | Jupiter’s ring system |
—
|
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: Jupiter’s ring system | Statement: [Adrastea, helpsSupplyMaterialTo, Jupiter’s ring system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpsSupplyMaterialTo Context triple: [Adrastea, helpsSupplyMaterialTo, Jupiter’s ring system]
-
A.
suppliesTo
Indicates that one entity provides or delivers goods, services, or resources to another entity.
-
B.
supplyBy
Indicates that one entity is provided, furnished, or made available by another entity as its source or supplier.
-
C.
materialProvidedFor
chosen
Indicates that one entity supplies or makes available a material for use, processing, or incorporation by another entity or purpose.
-
D.
suppliedMaterialType
Indicates the type or category of material that is provided or supplied in a given context.
-
E.
supplySituation
Indicates a relationship where one entity provides or makes available needed resources, goods, or services to another under specific conditions or circumstances.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa6345548190a52498ecb0a2f555 |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 5:36 p.m.