Triple
T3793419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaouite dynasty |
E89710
|
entity |
| Predicate | houseFoundedInYearApprox |
P13262
|
FINISHED |
| Object | 1630s |
—
|
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: 1630s | Statement: [Alaouite dynasty, houseFoundedInYearApprox, 1630s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseFoundedInYearApprox Context triple: [Alaouite dynasty, houseFoundedInYearApprox, 1630s]
-
A.
houseFounded
Indicates that an entity (such as a house, organization, or lineage) was established or created by another entity or at a specific time.
-
B.
yearBuilt
Indicates the specific year in which something (typically a structure or object) was constructed or completed.
-
C.
renovationYear
Indicates the year in which an entity underwent renovation or significant refurbishment.
-
D.
demolitionYearApprox
Indicates that an entity was demolished in or around a particular year, where the year is an approximate rather than an exact value.
-
E.
estimatedYearOfCreation
chosen
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
- 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_69aed9597d6881909b6ee3b9de859223 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecefa3608190a7a20ed6df6a64b2 |
completed | March 9, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69aee743c8d08190a9f9c97b836bd703 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.