Triple
T13465134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iconoclast Council of 754 |
E311475
|
entity |
| Predicate | participantsEstimated |
P1131
|
FINISHED |
| Object | around 300 bishops |
—
|
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: around 300 bishops | Statement: [Iconoclast Council of 754, participantsEstimated, around 300 bishops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participantsEstimated Context triple: [Iconoclast Council of 754, participantsEstimated, around 300 bishops]
-
A.
numberOfParticipants
chosen
Indicates the total count of entities involved in a particular event, activity, or relationship.
-
B.
approximateAudienceSize
Indicates an estimated number of individuals or entities that are expected to be reached or affected in a given context.
-
C.
estimatedMemberCount
Indicates the approximate or predicted number of members associated with an entity.
-
D.
guestCountApproximate
Indicates that the number of guests involved is represented as an estimated or approximate count rather than an exact figure.
-
E.
participantStrength
Indicates the degree or level of involvement, influence, or contribution that a participant has within a given event, interaction, or relationship.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0f1830819085700b4521e44678 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:41 p.m.