Triple
T23823496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monumento a Padre Anchieta em Santos |
E589300
|
entity |
| Predicate | creatorHasRole |
P48506
|
FINISHED |
| Object | modernist sculptor |
—
|
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: modernist sculptor | Statement: [Monumento a Padre Anchieta em Santos, creatorHasRole, modernist sculptor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creatorHasRole Context triple: [Monumento a Padre Anchieta em Santos, creatorHasRole, modernist sculptor]
-
A.
hasCreatorRoleFor
chosen
Indicates that an entity serves in the role of creator for another entity, establishing a creator-to-created relationship.
-
B.
hasAuthorRoleFor
Indicates that an entity serves in the role of author for another entity, such as a work, document, or publication.
-
C.
ownerRole
Indicates the role or capacity in which an entity serves as the owner of another entity.
-
D.
ownerOrFounder
Indicates that an entity either owns or has founded another entity, capturing both ownership and founding relationships.
-
E.
roleOnVoyager
Indicates the specific position, duty, or function an entity holds in relation to the Voyager mission or project.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7b12520819086daf8c284732e0f |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:59 p.m.