Triple
T34334305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maltese prehistoric culture |
E881102
|
entity |
| Predicate | endedAround |
P109063
|
FINISHED |
| Object | c. 1500 BC |
—
|
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: c. 1500 BC | Statement: [Maltese prehistoric culture, endedAround, c. 1500 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedAround Context triple: [Maltese prehistoric culture, endedAround, c. 1500 BC]
-
A.
endAround
chosen
Indicates that an event, process, or state concludes approximately at a specified time, location, or condition rather than at an exact, sharply defined endpoint.
-
B.
around
Indicates that one entity is located or moves on all or most sides of another entity, encircling or surrounding it spatially.
-
C.
endedWith
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
D.
heldAround
Indicates that one entity is held in a way that surrounds or encircles another entity.
-
E.
activeAround
Indicates that an entity is performing actions or exhibiting activity in the vicinity of another entity or location.
- 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_69f349ba96a08190b94887bae2d8ee49 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:58 a.m.