Triple
T36366005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rütli Oath |
E895624
|
entity |
| Predicate | hasCanonicalNumberOfSignatories |
P4946
|
FINISHED |
| Object | three |
—
|
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: three | Statement: [Rütli Oath, hasCanonicalNumberOfSignatories, three]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalNumberOfSignatories Context triple: [Rütli Oath, hasCanonicalNumberOfSignatories, three]
-
A.
hasApproximateNumberOfNativeSignatories
Indicates that an entity is associated with an estimated or approximate count of native signatories involved with it.
-
B.
hasSignatories
Indicates that one or more parties have formally signed or endorsed an agreement, document, or instrument.
-
C.
numberOfSignatories
chosen
Indicates the total count of entities that have formally signed or endorsed a given document, agreement, or item.
-
D.
initialSignatoriesCount
Indicates the number of entities that originally signed or agreed to a document, contract, or agreement at its inception.
-
E.
initialSignatoriesIncluded
Indicates that the specified entities were part of the original group that formally signed or endorsed an agreement or document.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffbe9e47688190a2692566dc326646 |
completed | May 9, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69ffbb7b45388190b62cbde5c2d435cd |
completed | May 9, 2026, 10:55 p.m. |
Created at: May 3, 2026, 4:10 p.m.