Triple
T9366580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sassanian drahm |
E225414
|
entity |
| Predicate | edgeType |
P88169
|
FINISHED |
| Object | plain edge |
—
|
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: plain edge | Statement: [Sassanian drahm, edgeType, plain edge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: edgeType Context triple: [Sassanian drahm, edgeType, plain edge]
-
A.
typicalEdge
Indicates a standard or representative connection between two entities, as opposed to a special or exceptional type of edge.
-
B.
formsEdgeOf
Indicates that one entity constitutes a boundary or outer limit of another entity.
-
C.
standardEdge
Indicates a basic or default connection or link between two entities, without any special properties or conditions.
-
D.
edgeTreatment
Indicates a relationship where a specific method or process is applied to modify, finish, or protect the edge of an object or material.
-
E.
linkType
Indicates the specific kind or category of relationship that connects two linked entities.
- 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_69ca842cbddc819099d71ecec48cf9e5 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5042c89c8190994b12cf7600c366 |
completed | April 1, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69cc7a6abb8c81908c7a2f4ee92cc949 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:43 p.m.