Triple
T9483749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taiwanese Romanization System |
E228709
|
entity |
| Predicate | canBeUsedAlongside |
P56284
|
FINISHED |
| Object | Chinese characters |
—
|
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: Chinese characters | Statement: [Taiwanese Romanization System, canBeUsedAlongside, Chinese characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeUsedAlongside Context triple: [Taiwanese Romanization System, canBeUsedAlongside, Chinese characters]
-
A.
canBeUsedOver
Indicates that one entity is suitable or valid for use in place of, or in relation to, another entity.
-
B.
canCoexistWith
chosen
Indicates that two entities are able to exist together in the same context or environment without conflict, interference, or mutual exclusion.
-
C.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
D.
canAlsoBe
Indicates that something has an additional possible state, role, or classification beyond its primary one.
-
E.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
- 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_69ca84730a5081908de282651019bf2f |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd804c859081908c261ad16b501f0d |
completed | April 1, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69cca561e6b0819090aa795f3c3a2083 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:55 p.m.