Triple
T31835447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Publius Vatinius |
E812657
|
entity |
| Predicate | wasMockedFor |
P61595
|
FINISHED |
| Object | physical deformities |
—
|
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: physical deformities | Statement: [Publius Vatinius, wasMockedFor, physical deformities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMockedFor Context triple: [Publius Vatinius, wasMockedFor, physical deformities]
-
A.
mockedBy
chosen
Indicates that one entity ridicules, teases, or makes fun of another entity.
-
B.
usedToBeCalled
Indicates that an entity previously had a different name or title than the one it currently has.
-
C.
mockupTesting
Indicates the process of evaluating and validating a design mockup by testing how well it meets intended requirements, usability, or user expectations.
-
D.
spiedFor
Indicates that one entity secretly gathered and provided information on behalf of another entity, typically an intelligence service or organization.
-
E.
wasResponseTo
Indicates that one event, action, or communication occurred as a direct reply or reaction to a preceding event, action, or communication.
- 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 30, 2026, 11:48 p.m.