Triple
T33942884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pamunkey |
E870211
|
entity |
| Predicate | paysAnnualTributeTo |
P113791
|
FINISHED |
| Object | Governor of Virginia |
—
|
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: Governor of Virginia | Statement: [Pamunkey, paysAnnualTributeTo, Governor of Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paysAnnualTributeTo Context triple: [Pamunkey, paysAnnualTributeTo, Governor of Virginia]
-
A.
paysHomageTo
Indicates that one entity formally shows respect, reverence, or honor toward another, often acknowledging its superiority, influence, or authority.
-
B.
subjectOfTribute
chosen
Indicates that one entity is the target or honoree of a tribute, such as a payment, offering, or act of respect made by another entity.
-
C.
typeOfTribute
Indicates the specific kind or category of tribute that is being given or required in a relationship.
-
D.
isPosthumousTributeTo
Indicates that something (such as a work, event, or honor) is created or given as a tribute to a person after that person has died.
-
E.
currencyOfTributeTo
Indicates the type of currency in which tribute is paid from one entity to another.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.