Triple
T26973103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NEWBORN |
E679372
|
entity |
| Predicate | initiallySignedBy |
P24721
|
FINISHED |
| Object | thousands of citizens |
—
|
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: thousands of citizens | Statement: [NEWBORN, initiallySignedBy, thousands of citizens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiallySignedBy Context triple: [NEWBORN, initiallySignedBy, thousands of citizens]
-
A.
typicallySignedWith
Indicates that an entity is most commonly or customarily accompanied by a particular signature, mark, or signing method.
-
B.
documentSignedBy
Indicates that a document has been formally signed or authorized by a specific entity.
-
C.
alsoSignedWith
Indicates that an entity signed or endorsed something together with another specified entity, as part of the same signing action or agreement.
-
D.
endSignedBy
Indicates that a document, agreement, or message is concluded with the signature or identifying mark of a specified party.
-
E.
initialSignatoriesIncluded
chosen
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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 6:40 a.m.