Triple
T477588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quarter Eagle |
E9094
|
entity |
| Predicate | relationToHalfEagle |
P14352
|
FINISHED |
| Object | half the value of a $5 Half Eagle coin |
—
|
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: half the value of a $5 Half Eagle coin | Statement: [Quarter Eagle, relationToHalfEagle, half the value of a $5 Half Eagle coin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToHalfEagle Context triple: [Quarter Eagle, relationToHalfEagle, half the value of a $5 Half Eagle coin]
-
A.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
B.
associatedHeir
Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
-
C.
isNephewOf
Indicates that one person is the male child of another person's sibling.
-
D.
historicalRelationship
Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
-
E.
moreDistantlyRelatedTo
Indicates that one entity is related to another by a more distant or indirect relationship compared to some closer reference relationship.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f03f3fbc81909af6e4496d5e6c2a |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf017548190ae38ff3314a1ffa3 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef06d2fc8190b379d575215a8518 |
completed | Feb. 28, 2026, 1:35 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.