Triple
T24769022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transylvania Company |
E619667
|
entity |
| Predicate | soughtApprovalFrom |
P19644
|
FINISHED |
| Object | Continental Congress |
—
|
NE NERFINISHED |
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: Continental Congress | Statement: [Transylvania Company, soughtApprovalFrom, Continental Congress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soughtApprovalFrom Context triple: [Transylvania Company, soughtApprovalFrom, Continental Congress]
-
A.
publicApproval
Indicates the degree to which the general public supports, agrees with, or has a favorable opinion of a person, action, policy, or entity.
-
B.
approvalFor
Indicates that one entity grants or has granted permission or consent for another entity’s action, request, or status.
-
C.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
D.
requiresAdviceAndApprovalOf
chosen
Indicates that one entity can proceed with an action or decision only if it first seeks guidance and obtains formal approval from another entity.
-
E.
approvedAt
Indicates the date and time at which an entity received formal approval.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a8dc8081909e2f4b65485a6786 |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:29 a.m.