Triple
T36656502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disputation XXXIII |
E905006
|
entity |
| Predicate | isPartOfNumberOfDisputations |
P95140
|
FINISHED |
| Object | 54 |
—
|
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: 54 | Statement: [Disputation XXXIII, isPartOfNumberOfDisputations, 54]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfNumberOfDisputations Context triple: [Disputation XXXIII, isPartOfNumberOfDisputations, 54]
-
A.
numberOfDisputations
chosen
Indicates the quantity of disputations (formal debates or arguments) associated with an entity.
-
B.
disputeInvolves
Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
-
C.
disputeSettlementParticipation
Indicates that an entity takes part in the process of resolving or settling a dispute.
-
D.
countIsDisputed
Indicates that the reported numerical value (such as a count, total, or tally) is contested or not agreed upon by relevant parties.
-
E.
contestedByUniversity
Indicates that a university formally challenges, disputes, or opposes something, such as a claim, decision, or status.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffe01c9d3c819084c256bb3c81c0dc |
completed | May 10, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ffdfcc78b08190aa4493f13d62a531 |
completed | May 10, 2026, 1:30 a.m. |
Created at: May 3, 2026, 4:11 p.m.