Triple
T19133127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | (386723) 2009 YE7 |
E468363
|
entity |
| Predicate | isNonResonant |
P134536
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [(386723) 2009 YE7, isNonResonant, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonResonant Context triple: [(386723) 2009 YE7, isNonResonant, true]
-
A.
isResonance
Indicates that one entity vibrates or responds in harmony with another, typically amplifying or reinforcing its effect or signal.
-
B.
isResonantBecause
Indicates that one entity resonates or harmonizes with another specifically due to a stated cause or underlying reason.
-
C.
isResonantObject
Indicates that one entity functions as an object capable of resonating (physically or metaphorically) in response to another entity or influence.
-
D.
isNonPeriodic
Indicates that the subject does not occur, repeat, or follow a pattern at regular intervals over time.
-
E.
resonanceWith
Indicates a relationship where one entity aligns, harmonizes, or meaningfully connects with another in a way that amplifies or reinforces its effect or significance.
- F. None of above. chosen
Provenance (4 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ea82f08190811ef35fbae744d1 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:05 p.m.