Triple
T33829956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 169P/NEAT |
E867067
|
entity |
| Predicate | isDynamicallyInfluencedBy |
P25489
|
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: [169P/NEAT, isDynamicallyInfluencedBy, Jupiter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDynamicallyInfluencedBy Context triple: [169P/NEAT, isDynamicallyInfluencedBy, Jupiter]
-
A.
isUnderInfluenceOf
Indicates that one entity is affected, controlled, or significantly shaped by the power, authority, or effect of another entity.
-
B.
hasPossibleInfluence
Indicates that one entity may have an effect on, contribute to, or shape the state, behavior, or outcome of another entity, without asserting that this influence is definite or direct.
-
C.
influencedByCurrent
Indicates that something’s state, behavior, or outcome is affected or determined by the current conditions, context, or situation.
-
D.
areAffectedBy
chosen
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
-
E.
hasSyntaxInfluenceFrom
Indicates that the syntax of one entity is influenced, shaped, or derived from the syntax of 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70022ccc88190abdc55e89e3d3172 |
completed | May 3, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.