Triple
T36024329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erard |
E1042082
|
entity |
| Predicate | nameUsageStatus |
P184340
|
FINISHED |
| Object | rare in modern times |
—
|
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: rare in modern times | Statement: [Erard, nameUsageStatus, rare in modern times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameUsageStatus Context triple: [Erard, nameUsageStatus, rare in modern times]
-
A.
nameStatus
Indicates the status or condition associated with an entity’s name, such as whether it is current, preferred, alternate, or deprecated.
-
B.
nameUsedSince
Indicates that a particular name has been in use for an entity starting from a specified point in time.
-
C.
namesakeStatus
Indicates that one entity serves as the namesake of another, or that two entities share a relationship based on having the same name.
-
D.
nameUsedIn
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
E.
nameUsedBy
Indicates that a particular name is employed or referenced by a specific entity.
- 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ad15f3b88190b7c9742a734fec5f |
completed | May 3, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7acad20388190b9b10270ca9bdfbc |
completed | May 3, 2026, 8:14 p.m. |
Created at: May 3, 2026, 4:07 p.m.