Triple
T33546688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seleucia in Isauria |
E859226
|
entity |
| Predicate | councilHeldIn |
P41597
|
FINISHED |
| Object | Council of Seleucia of 359 |
E242987
|
NE 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: Council of Seleucia of 359 | Statement: [Seleucia in Isauria, councilHeldIn, Council of Seleucia of 359]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: councilHeldIn Context triple: [Seleucia in Isauria, councilHeldIn, Council of Seleucia of 359]
-
A.
councilHeldHere
chosen
Indicates that a council or formal assembly took place at the specified location.
-
B.
councilHeldBetween
Indicates that a council, meeting, or formal deliberative session was held involving the two specified entities as participating parties.
-
C.
councilPresidedOverBy
Indicates that a council or formal assembly is led, directed, or overseen by a particular person or authority.
-
D.
heldCouncil
Indicates that an entity organized and conducted a formal meeting or assembly for discussion or decision-making with other participants.
-
E.
convenedIn
Indicates that an event, meeting, or formal gathering was brought together and held at a specific location.
- F. None of above.
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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f70c17d88190aa74afc2dd2a0467 |
completed | May 3, 2026, 7:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35a68cc7948190bb528e8da54ca499 |
completed | June 19, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:39 a.m.