Triple
T24983229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | siege of the Church of Saints Cyril and Methodius |
E625229
|
entity |
| Predicate | numberOfDefenders |
P63967
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [siege of the Church of Saints Cyril and Methodius, numberOfDefenders, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfDefenders Context triple: [siege of the Church of Saints Cyril and Methodius, numberOfDefenders, 7]
-
A.
hasNumberOfDefencemen
chosen
Indicates the relationship that specifies how many defencemen are associated with or assigned to a given entity.
-
B.
hasDefenderStrength
Indicates that an entity possesses a certain level or measure of defensive capability or protective power.
-
C.
defenderBase
Indicates that one entity serves as the primary defensive location or stronghold associated with another entity.
-
D.
defenderIn
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
-
E.
numberOfInvaders
Indicates the quantity of entities classified as invaders associated with a given subject or context.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 18, 2026, 6:02 a.m.