Triple
T33026509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Sea trade network |
E845055
|
entity |
| Predicate | approximatePeakCentury |
P198118
|
FINISHED |
| Object | 1st century CE |
—
|
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: 1st century CE | Statement: [Red Sea trade network, approximatePeakCentury, 1st century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximatePeakCentury Context triple: [Red Sea trade network, approximatePeakCentury, 1st century CE]
-
A.
approximateStartCentury
Indicates the century in which something is estimated or roughly believed to have begun.
-
B.
approximateUseEndCentury
Indicates that something’s period of use ended around, but not necessarily exactly in, a specified century.
-
C.
approximateReconstructionCentury
Indicates that an entity’s reconstruction date is estimated to fall within a specified century.
-
D.
approximateFlourishingStartCentury
Indicates the century in which an entity’s period of flourishing or peak activity is estimated to have begun.
-
E.
latestCentury
Indicates that the associated time or event occurs in, or belongs to, the most recent century relative to a given reference point.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
| PDg | Predicate description generation | batch_69fecb4be24481908bda6197d7fc32f4 |
completed | May 9, 2026, 5:51 a.m. |
Created at: May 1, 2026, 1:23 a.m.