Triple
T29411024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ventotene Manifesto |
E745893
|
entity |
| Predicate | draftedOn |
P166755
|
FINISHED |
| Object | Ventotene |
—
|
NE NERFINISHED |
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: Ventotene | Statement: [Ventotene Manifesto, draftedOn, Ventotene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: draftedOn Context triple: [Ventotene Manifesto, draftedOn, Ventotene]
-
A.
draftedAt
Indicates that an entity was selected or chosen by another entity at a specific draft event or position.
-
B.
draftedDuring
Indicates that an entity was formally selected or conscripted (e.g., into military service or a professional league) within the time span of a specified event or period.
-
C.
draftedIn
Indicates that one entity was selected or recruited into another entity (such as a team, organization, or military service) through a formal draft process.
-
D.
draftedUnder
Indicates that one entity was formally selected or conscripted into a role, position, or service according to the authority, rules, or jurisdiction of another entity.
-
E.
draftedFor
Indicates that one entity has been selected or assigned, typically through a draft process, to serve, play, or work for another entity.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a38eed0819096f7950f54d4a3fa |
completed | May 2, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 28, 2026, 2:57 p.m.