Triple
T26396948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourth Pre-Conciliar Pan-Orthodox Conference |
E663587
|
entity |
| Predicate | ordinalNumberInSeries |
P4901
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Fourth Pre-Conciliar Pan-Orthodox Conference, ordinalNumberInSeries, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordinalNumberInSeries Context triple: [Fourth Pre-Conciliar Pan-Orthodox Conference, ordinalNumberInSeries, 4]
-
A.
ordinalNumber
chosen
Indicates the position or rank of an entity within an ordered sequence (e.g., first, second, third).
-
B.
hasOrdinalSeries
Indicates that one entity belongs to, or is positioned within, an ordered sequence or series relative to other entities.
-
C.
ordinalInOffice
Indicates the numerical order or rank of an individual’s term or tenure in a particular office or position.
-
D.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
E.
positionHeldInSeries
Indicates the specific role or placement an entity occupies within an ordered sequence or series.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610c3adc481908a3df0856345498f |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:29 p.m.