Triple
T33063105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLPA |
E846023
|
entity |
| Predicate | targetDialect |
P107908
|
FINISHED |
| Object | Xiamen |
—
|
NE NERFINISHED |
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: Xiamen | Statement: [TLPA, targetDialect, Xiamen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetDialect Context triple: [TLPA, targetDialect, Xiamen]
-
A.
usesDialect
Indicates that one entity communicates or expresses itself using the specific dialect associated with another entity.
-
B.
implementsDialectOf
Indicates that one entity realizes or carries out a specific dialect, variant, or localized form of another entity (such as a language, standard, or protocol).
-
C.
associatedWithDialect
chosen
Indicates a relationship where something is linked or connected to a particular dialect, such as being characteristic of, derived from, or used within that dialect.
-
D.
isBasedOnDialect
Indicates that something (such as a language variety, system, or representation) is derived from, structured around, or primarily influenced by a particular dialect.
-
E.
affectsDialect
Indicates that one entity influences or changes the dialect used or spoken by another entity.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: May 1, 2026, 1:25 a.m.