Triple
T37124635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montaigne’s tower |
E919356
|
entity |
| Predicate | dedicatedToActivity |
P187644
|
FINISHED |
| Object | reading |
—
|
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: reading | Statement: [Montaigne’s tower, dedicatedToActivity, reading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dedicatedToActivity Context triple: [Montaigne’s tower, dedicatedToActivity, reading]
-
A.
oftenDedicatedTo
Indicates that something is frequently or habitually devoted, assigned, or committed to a particular purpose, activity, or recipient.
-
B.
dedicatedToConcept
Indicates that something is specifically devoted, committed, or purposefully directed toward a particular concept or abstract idea.
-
C.
targetedActivity
Indicates that an activity is specifically directed or focused toward a particular entity, group, or objective.
-
D.
dedicated
Indicates that one entity is formally assigned, reserved, or committed for the specific use, benefit, or purpose of another entity.
-
E.
dedicatedOnOccasionOf
Indicates that something (typically a work, object, or event) is formally dedicated in connection with or to commemorate a particular occasion.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb78c982ac8190846efe8f6209e5d1 |
completed | May 6, 2026, 5:22 p.m. |
Created at: May 3, 2026, 4:15 p.m.