Triple
T35322310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipality of Voies |
E1020071
|
entity |
| Predicate | partOfAfter2011 |
P38393
|
FINISHED |
| Object | municipality of Monemvasia |
—
|
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: municipality of Monemvasia | Statement: [municipality of Voies, partOfAfter2011, municipality of Monemvasia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfAfter2011 Context triple: [municipality of Voies, partOfAfter2011, municipality of Monemvasia]
-
A.
partOfAfter
chosen
Indicates that one entity becomes a component or subset of another entity at some point after a specified time or event.
-
B.
hasPartInYear
Indicates that something includes or contains a specific part, component, or segment that is associated with a particular year.
-
C.
concludingPartOf
Indicates that one entity serves as the final or closing section of another entity, bringing it to an end.
-
D.
tookPlaceAfter
Indicates that one event or occurrence happened later in time than another event or occurrence.
-
E.
consideredPartOf
Indicates that one entity is regarded or treated as a component, segment, or subset of another entity within a larger whole.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00818b20a881909fbf3bb33dcf7029 |
completed | May 10, 2026, 1 p.m. |
| PD | Predicate disambiguation | batch_6a0080f76f588190a933238861243d1a |
completed | May 10, 2026, 12:58 p.m. |
Created at: May 3, 2026, 4:03 p.m.