Triple
T17655721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Serdica |
E429615
|
entity |
| Predicate | hadParticipationFrom |
P74692
|
FINISHED |
| Object | Latin-speaking West |
—
|
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: Latin-speaking West | Statement: [Council of Serdica, hadParticipationFrom, Latin-speaking West]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadParticipationFrom Context triple: [Council of Serdica, hadParticipationFrom, Latin-speaking West]
-
A.
endedParticipationOf
Indicates that one entity caused or marked the termination of another entity’s involvement in an activity, event, or relationship.
-
B.
hasBeenInvolvedIn
chosen
Indicates that an entity has participated in, taken part in, or been connected to a particular event, activity, or situation.
-
C.
participatedInEvent
Indicates that an entity took part in or was actively involved in a specific event.
-
D.
hasFormerParticipant
Indicates that an entity once participated in an activity, event, or organization but is no longer a current participant.
-
E.
coParticipantIn
Indicates that two or more entities take part together as participants in the same event, activity, or situation.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46e40e344819086a49c69f8f2956b |
completed | April 19, 2026, 5:55 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 6:06 a.m.