Triple
T2998124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States quarter dollar coin |
E81119
|
entity |
| Predicate | hasEdge |
P44914
|
FINISHED |
| Object | reeded 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: reeded edge | Statement: [United States quarter dollar coin, hasEdge, reeded edge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEdge Context triple: [United States quarter dollar coin, hasEdge, reeded edge]
-
A.
hasVertex
Indicates that an object, typically a geometric shape or graph, includes a specified vertex as one of its corner or node points.
-
B.
hasJunctionWith
Indicates that one entity meets or intersects with another at a shared junction point.
-
C.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
D.
hasJunctionIn
Indicates that one entity contains or includes a junction located within the spatial or structural extent of another entity.
-
E.
hasConnectedComponent
Indicates that one entity includes or is associated with a specific connected component as part of its structure or decomposition.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f766408190a5591efce8346bb9 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 2:59 p.m.