Triple
T23015964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charter 08 |
E573029
|
entity |
| Predicate | numberOfInitialSignatories |
P7971
|
FINISHED |
| Object | 303 |
—
|
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: 303 | Statement: [Charter 08, numberOfInitialSignatories, 303]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfInitialSignatories Context triple: [Charter 08, numberOfInitialSignatories, 303]
-
A.
initialSignatoriesCount
chosen
Indicates the number of entities that originally signed or agreed to a document, contract, or agreement at its inception.
-
B.
numberOfSignatories
Indicates the total count of entities that have formally signed or endorsed a given document, agreement, or item.
-
C.
laterSignatoriesCount
Indicates the number of other entities that became signatories after the referenced entity.
-
D.
initialSignatoriesIncluded
Indicates that the specified entities were part of the original group that formally signed or endorsed an agreement or document.
-
E.
estimatedNumberOfSignatures
Indicates the approximate count of signatures associated with or required for a given item, action, or agreement.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183e4dcd48190b2b1c2ab43205e41 |
completed | April 29, 2026, 4:07 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.