Triple
T5781055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galloway Plan of Union |
E127555
|
entity |
| Predicate | rejectionMethod |
P438
|
FINISHED |
| Object | vote of the Continental Congress |
—
|
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: vote of the Continental Congress | Statement: [Galloway Plan of Union, rejectionMethod, vote of the Continental Congress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rejectionMethod Context triple: [Galloway Plan of Union, rejectionMethod, vote of the Continental Congress]
-
A.
rejectedBy
chosen
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
B.
rejectedIn
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
-
C.
rejectedAt
Indicates the time or date at which something (such as a request, application, or proposal) was formally rejected.
-
D.
rejectedBecause
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
-
E.
mayReject
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
- 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_69c008361fa88190aefa4dc41b051e7f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029e3f88c8190975921ff2912e543 |
completed | March 22, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:50 p.m.