Triple
T896222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oort cloud |
E19351
|
entity |
| Predicate | mayOverlapWith |
P1867
|
FINISHED |
| Object | local interstellar medium |
—
|
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: local interstellar medium | Statement: [Oort cloud, mayOverlapWith, local interstellar medium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayOverlapWith Context triple: [Oort cloud, mayOverlapWith, local interstellar medium]
-
A.
overlapsWith
chosen
Indicates that two entities share a common part or region in space, time, or extent, but neither is completely contained within the other.
-
B.
mayExtendTo
Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
-
C.
mayMeet
Indicates that one entity is permitted or has the possibility to meet or come together with another entity.
-
D.
coincidesWith
Indicates that two entities occupy the same position, time, or state such that they exactly overlap or occur together.
-
E.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad23d6e88190a2fb5e1e168a7b44 |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa94f7c881908deeb62308942e19 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.