Triple
T12656522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randolph Plan |
E302297
|
entity |
| Predicate | proposedByDelegation |
P55527
|
FINISHED |
| Object | Virginia delegation |
—
|
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: Virginia delegation | Statement: [Randolph Plan, proposedByDelegation, Virginia delegation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedByDelegation Context triple: [Randolph Plan, proposedByDelegation, Virginia delegation]
-
A.
wereProposedBy
Indicates that one or more entities (such as ideas, plans, or items) were put forward or suggested by a specific agent or source.
-
B.
coProposedBy
chosen
Indicates that a proposal, idea, or item is jointly put forward or suggested by multiple entities together.
-
C.
mayBeDelegatedTo
Indicates that a responsibility, task, or authority can be transferred from one entity to another to act on its behalf.
-
D.
acceptedOnBehalfOf
Indicates that one party formally accepts something (such as an offer, agreement, or responsibility) while acting as a representative or proxy for another party.
-
E.
canDelegateTo
Indicates that one entity has the authority or ability to transfer or assign its responsibilities, tasks, or decision-making power to another entity.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b78ce8819091f15dd5013e6da5 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:18 p.m.