Triple
T24320969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Said |
E612960
|
entity |
| Predicate | periodOfContinuousRule |
P131991
|
FINISHED |
| Object | mid-18th century to present |
—
|
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: mid-18th century to present | Statement: [Al Said, periodOfContinuousRule, mid-18th century to present]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfContinuousRule Context triple: [Al Said, periodOfContinuousRule, mid-18th century to present]
-
A.
establishedPeriod
Indicates the time span or date range during which something was founded, created, or formally brought into existence.
-
B.
agingPeriod
Indicates the length of time something is allowed or intended to mature or age before reaching its final or usable state.
-
C.
administrationPeriod
chosen
Indicates the time span during which an entity is responsible for administering, managing, or governing another entity or resource.
-
D.
continuedIntoPeriod
Indicates that an action, state, or relationship that began earlier persisted without interruption into a specified later time period.
-
E.
appliedDuringPeriod
Indicates that an action, condition, or status was in effect throughout a specified time period.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292ab2fa08190bc19c3edc0a1a9b2 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:50 a.m.