Triple
T8655983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hernando Pizarro |
E205415
|
entity |
| Predicate | typeOfAdminRole |
P5518
|
FINISHED |
| Object | colonial landholder |
—
|
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: colonial landholder | Statement: [Hernando Pizarro, typeOfAdminRole, colonial landholder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAdminRole Context triple: [Hernando Pizarro, typeOfAdminRole, colonial landholder]
-
A.
hasAdministrativeType
Indicates that an entity is associated with a specific category or level of administrative classification (such as type of jurisdiction or administrative unit).
-
B.
typeOfRole
chosen
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
C.
ownerRole
Indicates the role or capacity in which an entity serves as the owner of another entity.
-
D.
definesRole
Indicates that one entity specifies or establishes the role, function, or position of another entity within a given context.
-
E.
ClientRole
Indicates that an entity participates in a relationship or interaction specifically in the capacity of a client.
- 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_69ca8350897c819086cde7596fbe5fe7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4844586081909b687e278496eefa |
completed | March 31, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.