Triple
T12576464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clear script |
E300217
|
entity |
| Predicate | stillInUseStatus |
P65653
|
FINISHED |
| Object | limited contemporary use |
—
|
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: limited contemporary use | Statement: [Clear script, stillInUseStatus, limited contemporary use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stillInUseStatus Context triple: [Clear script, stillInUseStatus, limited contemporary use]
-
A.
isInUse
Indicates that an entity is currently being utilized or actively engaged in its intended function or operation.
-
B.
stillUsedBy
Indicates that something continues to be used or relied upon by another entity at the present time.
-
C.
usageStatus
chosen
Indicates the current state or condition of how something is being used, such as whether it is active, inactive, available, or in use.
-
D.
availabilityStatus
Indicates the current state of whether something is obtainable, usable, or accessible at a given time.
-
E.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9550d84908190aea0f50055f6d92e |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95414692881909c52a1de7d224b44 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 4:47 p.m.