Triple
T27149311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jarrow March |
E682339
|
entity |
| Predicate | petitionSignatures |
P161911
|
FINISHED |
| Object | about 12,000 |
—
|
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: about 12,000 | Statement: [Jarrow March, petitionSignatures, about 12,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: petitionSignatures Context triple: [Jarrow March, petitionSignatures, about 12,000]
-
A.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
B.
noteSignature
Indicates that one entity serves as a signature or identifying mark attached to a note created or associated with another entity.
-
C.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
D.
sharesSignsWith
Indicates that two entities exhibit the same or overlapping signs, symptoms, or observable indicators.
-
E.
signatoryForce
Indicates that an entity has the authority or power to sign or bind an agreement, treaty, or contract on behalf of a party.
- F. None of above. chosen
Provenance (4 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f624c8b4148190990ea6bd13e9e271 |
completed | May 2, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fa35ac48190890102c348ed81a0 |
completed | May 2, 2026, 4 p.m. |
Created at: April 27, 2026, 9:13 a.m.