Triple
T21396767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilanun |
E527805
|
entity |
| Predicate | historicalPeriodOfRaiding |
P143813
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Ilanun, historicalPeriodOfRaiding, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfRaiding Context triple: [Ilanun, historicalPeriodOfRaiding, 18th century]
-
A.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
B.
historicalPeriodOfGreatestDanger
Indicates the time period in which an entity faced its highest level of risk, threat, or vulnerability.
-
C.
conquestPeriod
Indicates the time span during which one entity successfully subjugates or takes control of another through conquest.
-
D.
historicalPeriodOfMajorContact
Indicates the historical time period during which the most significant or intensive contact occurred between the related entities.
-
E.
historicalEraOfRise
Indicates the historical era or period during which an entity first rose to prominence, influence, or significance.
- F. None of above. chosen
Provenance (4 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_69e0b51ff3748190935c0a513c62a12b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b11a2aec8190a60e53b90d0823b1 |
completed | April 22, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 5:13 p.m.