Triple
T897660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Room |
E19378
|
entity |
| Predicate | currentStructureDate |
P6878
|
FINISHED |
| Object | Crusader period |
—
|
LITERAL FINISHED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentStructureDate Context triple: [Upper Room, currentStructureDate, Crusader period]
-
A.
dateOf
chosen
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
B.
date
Indicates that two entities are engaged in or participate in a romantic or social outing or relationship with each other.
-
C.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
D.
integrationDate
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
-
E.
datePresented
Indicates the date on which something (such as an item, work, or information) was formally presented or made known to an audience or recipient.
- F. None of above.
Provenance (2 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69a4aa9635608190a297e2067b8dcee2 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.