Triple
T29645089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of the Patriarchs |
E755975
|
entity |
| Predicate | hasBestViewingTime |
P150574
|
FINISHED |
| Object | morning |
—
|
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: morning | Statement: [Court of the Patriarchs, hasBestViewingTime, morning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBestViewingTime Context triple: [Court of the Patriarchs, hasBestViewingTime, morning]
-
A.
typicalViewingTime
Indicates the usual or most common amount of time an entity is viewed or watched under normal circumstances.
-
B.
minimumViewingTime
Indicates the least amount of time an item must be viewed or played for a condition (such as completion, eligibility, or credit) to be considered satisfied.
-
C.
observationBestTime
chosen
Indicates that there is an identified optimal or most suitable time period during which the observation of something should be made.
-
D.
showsTimeOf
Indicates that one entity displays or reveals the specific time at which another entity occurs or is scheduled.
-
E.
viewingIs
Indicates that one entity is engaged in the act or state of viewing, observing, or watching another entity.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 28, 2026, 6:49 p.m.