Triple
T1877545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sundanese script |
E39177
|
entity |
| Predicate | modernRevival |
P9802
|
FINISHED |
| Object | revived in the late 20th and early 21st centuries |
—
|
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: revived in the late 20th and early 21st centuries | Statement: [Sundanese script, modernRevival, revived in the late 20th and early 21st centuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernRevival Context triple: [Sundanese script, modernRevival, revived in the late 20th and early 21st centuries]
-
A.
modernUse
Indicates how something is currently used or applied in modern times.
-
B.
modernizationPeriod
Indicates the time span during which an entity undergoes or is subject to modernization efforts or processes.
-
C.
modernization
Indicates a process by which something is updated, reformed, or transformed to align with contemporary standards, technologies, or practices.
-
D.
modernState
Indicates that an entity functions as a contemporary, currently existing state or nation in the modern era.
-
E.
revival
chosen
Indicates the act of bringing something back into use, popularity, or active existence after a period of decline, dormancy, or disuse.
- 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_69a8862f7074819096afe7fe65e179e9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb0f79fbc819085c54f3189a552d9 |
completed | March 7, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69abafe2b56c81909e13d543982e6e13 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.