Triple
T20613065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IC 2163 |
E506494
|
entity |
| Predicate | hasDisturbanceCause |
P708
|
FINISHED |
| Object | gravitational interaction with NGC 2207 |
—
|
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: gravitational interaction with NGC 2207 | Statement: [IC 2163, hasDisturbanceCause, gravitational interaction with NGC 2207]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisturbanceCause Context triple: [IC 2163, hasDisturbanceCause, gravitational interaction with NGC 2207]
-
A.
hasCause
chosen
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
-
B.
hasInterference
Indicates that one entity negatively affects or obstructs the normal function, performance, or occurrence of another entity or process.
-
C.
canBeDisturbedBy
Indicates that an entity is susceptible to being interrupted, bothered, or otherwise negatively affected by another entity or factor.
-
D.
hasProposedCause
Indicates that one entity is suggested or hypothesized to be the cause or explanation for another entity or event.
-
E.
hasAnomaly
Indicates that an entity exhibits, contains, or is associated with an irregular, abnormal, or unexpected condition or feature.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aad94dac8190921c7769a649c724 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.