Triple
T36847817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sines historic center |
E910598
|
entity |
| Predicate | periodOfMainDevelopment |
P53998
|
FINISHED |
| Object | Middle Ages |
—
|
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: Middle Ages | Statement: [Sines historic center, periodOfMainDevelopment, Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfMainDevelopment Context triple: [Sines historic center, periodOfMainDevelopment, Middle Ages]
-
A.
developedFromPeriod
Indicates that something originated, evolved, or was derived from a specified historical or temporal period.
-
B.
eraOfPrimaryDevelopment
chosen
Indicates the time period during which something was primarily developed or formed.
-
C.
historicalPeriodOfRapidDevelopment
Indicates a time span during which something undergoes unusually fast or intense growth, change, or advancement compared to other periods.
-
D.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
-
E.
partOfDevelopment
Indicates that one entity is a component, phase, or contributing element within the overall development process of 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:13 p.m.