Triple
T16296928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humboldtianum |
E395670
|
entity |
| Predicate | observationAffectedBy |
P25489
|
FINISHED |
| Object | libration |
—
|
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: libration | Statement: [Humboldtianum, observationAffectedBy, libration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observationAffectedBy Context triple: [Humboldtianum, observationAffectedBy, libration]
-
A.
areAffectedBy
chosen
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
-
B.
affectsPhenomenon
Indicates that one phenomenon produces an influence or change on another phenomenon.
-
C.
affectedControlOf
Indicates that one entity has influenced, altered, or impacted the degree of control another entity has over something.
-
D.
effectOnOthers
Indicates the impact or influence that one entity’s actions, presence, or state has on other entities.
-
E.
affectedRecord
Indicates that one entity is a record that is impacted, modified, or otherwise influenced as a result of an action or event involving 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e2dcdac819083918f0964dd5666 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.