Triple
T18075797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Filitosa |
E432548
|
entity |
| Predicate | mainOccupationDate |
P124309
|
FINISHED |
| Object | 3rd millennium BCE |
—
|
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: 3rd millennium BCE | Statement: [Filitosa, mainOccupationDate, 3rd millennium BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainOccupationDate Context triple: [Filitosa, mainOccupationDate, 3rd millennium BCE]
-
A.
laterOccupationApproxDate
Indicates an approximate date or time period when a subject began a subsequent occupation or role after an earlier one.
-
B.
earliestOccupationDate
Indicates the earliest known date on which an entity began a particular occupation or role.
-
C.
memberLaterOccupation
Indicates that an individual later held a particular occupation or position after an earlier point in time or role.
-
D.
timeOfMainOccupation
chosen
Indicates the specific time period during which an entity primarily carries out its main occupation or activity.
-
E.
hadOccupationStatusUntil
Indicates that an entity held a particular occupational status up to, but not necessarily beyond, a specified point in time.
- 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4d9f4f76c81909015ae4d66d1c85f |
completed | April 19, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:26 a.m.