Triple
T38518387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jalen |
E922400
|
entity |
| Predicate | isModernCoinage |
P49135
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Jalen, isModernCoinage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isModernCoinage Context triple: [Jalen, isModernCoinage, true]
-
A.
coinageFeature
Indicates a characteristic, design element, or attribute that is present on or associated with a particular coin or type of coinage.
-
B.
isModern
chosen
Indicates that something belongs to, reflects, or is characteristic of the contemporary or recent period, especially in style, design, or thinking.
-
C.
coinageDate
Indicates the date or time period when a coin (or currency unit) was first minted or officially issued.
-
D.
laterCoinageStyle
Indicates that one entity’s style or design is modeled after, influenced by, or characteristic of a later period of coinage relative to another.
-
E.
coinageType
Indicates the specific type or category of coinage associated with an entity, such as its denomination, series, or monetary classification.
- 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_69f76ea5f5588190bd0b28c82e975640 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.