Triple
T9297897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JP-7 |
E223685
|
entity |
| Predicate | noLongerInWidespreadUse |
P46419
|
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: [JP-7, noLongerInWidespreadUse, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: noLongerInWidespreadUse Context triple: [JP-7, noLongerInWidespreadUse, true]
-
A.
abolishedInPractice
chosen
Indicates that, although not formally revoked, the action or institution is no longer carried out or enforced in actual practice.
-
B.
historicalUsageDeclinedAfter
Indicates that the frequency or prevalence of using something has decreased after a specified time, event, or condition.
-
C.
usedInsteadOf
Indicates that one entity is employed or chosen as a substitute or replacement for another entity.
-
D.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
E.
notTypicallyUsedFor
Indicates that something is generally not used for a particular purpose, function, or activity under normal circumstances.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd089e3ae88190aa4181cdd85a67b8 |
completed | April 1, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.