Triple
T19074816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millenary Petition |
E466876
|
entity |
| Predicate | signatoriesClaimedNumber |
P119757
|
FINISHED |
| Object | around one thousand ministers |
—
|
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 one thousand ministers | Statement: [Millenary Petition, signatoriesClaimedNumber, around one thousand ministers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatoriesClaimedNumber Context triple: [Millenary Petition, signatoriesClaimedNumber, around one thousand ministers]
-
A.
numberOfSignatories
Indicates the total count of entities that have formally signed or endorsed a given document, agreement, or item.
-
B.
laterSignatoriesCount
Indicates the number of other entities that became signatories after the referenced entity.
-
C.
estimatedNumberOfSignatures
chosen
Indicates the approximate count of signatures associated with or required for a given item, action, or agreement.
-
D.
hasSignatories
Indicates that one or more parties have formally signed or endorsed an agreement, document, or instrument.
-
E.
signCount
Indicates the number of signs associated with, produced by, or present in relation to a given entity 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e3c7b08190bf6448ead11ba916 |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.