Triple
T2153987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bab al-Kaaba |
E47843
|
entity |
| Predicate | currentDesignPeriod |
P4988
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Bab al-Kaaba, currentDesignPeriod, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentDesignPeriod Context triple: [Bab al-Kaaba, currentDesignPeriod, 20th century]
-
A.
hasDesignPeriod
Indicates that something was created, planned, or developed during a specified historical or stylistic design period.
-
B.
designPeriod
Indicates the time span during which something is planned, designed, or conceptually developed before implementation or production.
-
C.
currentDesignInForceSince
chosen
Indicates the date or point in time from which the current design has been officially in effect or valid.
-
D.
designYear
Indicates the year in which something was originally designed or conceived.
-
E.
designLifetime
Indicates the intended duration or operational period for which something is designed to function as specified.
- 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe4a3b608190b3bd5d8e28534090 |
completed | March 7, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69abbd9a60648190b20b116be5c7ad98 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.