Triple
T24572527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb of Eurysaces the Baker |
E607999
|
entity |
| Predicate | honorsSocialStatus |
P337
|
FINISHED |
| Object | wealthy freedman |
—
|
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: wealthy freedman | Statement: [Tomb of Eurysaces the Baker, honorsSocialStatus, wealthy freedman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsSocialStatus Context triple: [Tomb of Eurysaces the Baker, honorsSocialStatus, wealthy freedman]
-
A.
honors
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
-
B.
honorLevel
chosen
Indicates the degree or status of respect, distinction, or recognition accorded to an entity relative to others.
-
C.
honorsRole
Indicates that one entity formally recognizes and respects the position, title, or role held by another entity.
-
D.
confersHonorificStatus
Indicates that one entity formally grants an honorific title, rank, or status to another entity.
-
E.
nameHonors
Indicates that a name is given to honor, commemorate, or pay tribute to a particular entity.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9269360819090c44f4483c3533c |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:28 a.m.