Triple
T32240711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Jaghbub |
E823603
|
entity |
| Predicate | periodAsSenussiCenterEnd |
P102590
|
FINISHED |
| Object | early 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: early 20th century | Statement: [Al-Jaghbub, periodAsSenussiCenterEnd, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodAsSenussiCenterEnd Context triple: [Al-Jaghbub, periodAsSenussiCenterEnd, early 20th century]
-
A.
focusPeriodEnd
Indicates the point in time at which a specified focus period or interval concludes.
-
B.
periodizedAs
Indicates that something has been divided or organized into distinct time periods according to a particular periodization scheme.
-
C.
periodProperty
Indicates a temporal characteristic or attribute associated with a specific time period or interval.
-
D.
periodReception
Indicates a temporal relationship where one entity receives, hosts, or is associated with another during a specific time period or interval.
-
E.
timePeriodAsCenterUntil
chosen
Indicates that a time period is considered the central reference point and extends up to, but not beyond, a specified endpoint in time.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 12:40 a.m.