Triple
T3846408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cerveteri |
E93579
|
entity |
| Predicate | wasPowerfulIn |
P51895
|
FINISHED |
| Object | Etruscan period |
—
|
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: Etruscan period | Statement: [Cerveteri, wasPowerfulIn, Etruscan period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasPowerfulIn Context triple: [Cerveteri, wasPowerfulIn, Etruscan period]
-
A.
wasA
Indicates that an entity previously had a certain role, type, or classification in the past.
-
B.
hadExecutivePowerIn
Indicates that an entity held executive authority or governing power within a specified organization, institution, or jurisdiction during a certain period.
-
C.
hasSuperpower
Indicates that one entity possesses a special or extraordinary power or ability beyond normal human capabilities.
-
D.
cameToPowerThrough
Indicates the manner or process by which an entity attained authority, leadership, or control, specifying how it rose to power.
-
E.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeebb77a488190be7fc2a1211f1f2d |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee8d9b328819080158be59e5bcc97 |
completed | March 9, 2026, 3:35 p.m. |
Created at: March 9, 2026, 3:18 p.m.