Triple
T27039582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gwoyeu Romatzyh |
E684449
|
entity |
| Predicate | timeInUseAsOfficialSystem |
P2451
|
FINISHED |
| Object | 1928–1940s |
—
|
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: 1928–1940s | Statement: [Gwoyeu Romatzyh, timeInUseAsOfficialSystem, 1928–1940s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInUseAsOfficialSystem Context triple: [Gwoyeu Romatzyh, timeInUseAsOfficialSystem, 1928–1940s]
-
A.
usedAsOfficialTime
Indicates that something is employed as the recognized standard or authoritative reference for measuring time in an official context.
-
B.
timeSystem
Indicates a relationship where an entity uses, follows, or is defined within a particular system for measuring or organizing time.
-
C.
inUseSince
chosen
Indicates that an entity has been actively in use starting from a specified point in time.
-
D.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
-
E.
replacedSystemUsedUntil
Indicates that one system was used up until it was replaced by another system.
- 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_69ef148193c48190bb1a0cfae6a407c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 8:03 a.m.