Triple
T19839973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Peoples |
E476699
|
entity |
| Predicate | uncertain |
P9983
|
FINISHED |
| Object | exact ethnic origins |
—
|
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: exact ethnic origins | Statement: [Sea Peoples, uncertain, exact ethnic origins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uncertain Context triple: [Sea Peoples, uncertain, exact ethnic origins]
-
A.
uncertainty
chosen
Indicates that there is doubt, lack of sureness, or incomplete confidence about a fact, outcome, or state of affairs in the relationship or situation described.
-
B.
hasUncertainNature
Indicates that the nature, status, or characteristics of the relationship or situation are not clearly defined, known, or determined.
-
C.
hasUncertainForm
Indicates that the form or structure of something is not clearly defined, fixed, or confidently known.
-
D.
hasUncertainty
Indicates that the relationship or value is associated with some level or type of uncertainty rather than being fully definite or precise.
-
E.
hasUncertainFate
Indicates that the outcome, status, or future of the related entity or event is unknown, unresolved, or not clearly determined.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65804be608190b49e110c3bf381bc |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:50 p.m.