Triple
T31133835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prophet's Mosque courtyard |
E793583
|
entity |
| Predicate | experiencesPeakUseDuring |
P86087
|
FINISHED |
| Object | Ramadan |
—
|
NE NERFINISHED |
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: Ramadan | Statement: [Prophet's Mosque courtyard, experiencesPeakUseDuring, Ramadan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencesPeakUseDuring Context triple: [Prophet's Mosque courtyard, experiencesPeakUseDuring, Ramadan]
-
A.
usagePeak
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
-
B.
peakUse
Indicates the time, condition, or context in which something reaches its maximum level of use or intensity.
-
C.
hasPeakVisitationSeason
Indicates that an entity experiences its highest or most concentrated level of visitation during a specific season or time period.
-
D.
hasTimeOfHighActivity
chosen
Indicates that an entity experiences its peak or most intense level of activity during a specified time period.
-
E.
approximateUserPeak
Indicates that one value or event is an estimated or inferred maximum point associated with a particular user.
- 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:05 p.m.