Triple
T4405724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garden of Gethsemane |
E93727
|
entity |
| Predicate | functionHistorically |
P2715
|
FINISHED |
| Object | olive grove |
—
|
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: olive grove | Statement: [Garden of Gethsemane, functionHistorically, olive grove]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionHistorically Context triple: [Garden of Gethsemane, functionHistorically, olive grove]
-
A.
historicalFunction
chosen
Indicates the role, purpose, or activity an entity had during a past period or in a historical context.
-
B.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
C.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
D.
historicalStatusOf
Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
-
E.
operatorHistory
Indicates a record of past actions, states, or changes associated with a particular operator over time.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b35489f6948190a4b2c259f64b4abf |
completed | March 13, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:28 p.m.