Triple
T22530830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plot D |
E557030
|
entity |
| Predicate | gravesMarking |
P148532
|
FINISHED |
| Object | simple grave markers without honors |
—
|
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: simple grave markers without honors | Statement: [Plot D, gravesMarking, simple grave markers without honors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gravesMarking Context triple: [Plot D, gravesMarking, simple grave markers without honors]
-
A.
facialMarkings
Indicates that one entity has distinctive marks, patterns, or features on its face in relation to another entity or context.
-
B.
eggMarkings
Indicates that one entity bears or displays specific markings or patterns on its eggs in relation to another entity or context.
-
C.
armorMarkings
Indicates that one entity bears specific markings, patterns, or insignia on its armor in relation to another entity or context.
-
D.
lightingMarks
Indicates that one entity applies or provides lighting effects or illumination to another entity or location.
-
E.
distinctiveMarking
Indicates that one entity bears a unique or distinguishing visual feature or pattern that sets it apart from others.
- F. None of above. chosen
Provenance (4 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed6734881908abbbee477dfab98 |
completed | April 29, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:51 p.m.