Triple
T5044834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Convent |
E113636
|
entity |
| Predicate | centralEventLocation |
P49732
|
FINISHED |
| Object | climactic attack by men from Ruby |
—
|
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: climactic attack by men from Ruby | Statement: [the Convent, centralEventLocation, climactic attack by men from Ruby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralEventLocation Context triple: [the Convent, centralEventLocation, climactic attack by men from Ruby]
-
A.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
B.
locationOfEventDescribed
chosen
Indicates that one entity is the place or setting where the event described by another entity occurs.
-
C.
centerType
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an entity.
-
D.
centralCeremonyLocation
Indicates the place that serves as the primary or focal site where a ceremony is held.
-
E.
eventLocationOfNotableActivity
Indicates that a location is the place where a notable or significant activity or event involving the related entity occurred.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73fd81788190b7799f519277119a |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.