Triple
T33063084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLPA |
E846023
|
entity |
| Predicate | appliesToLanguageGroup |
P1129
|
FINISHED |
| Object | Southern Min |
—
|
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: Southern Min | Statement: [TLPA, appliesToLanguageGroup, Southern Min]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToLanguageGroup Context triple: [TLPA, appliesToLanguageGroup, Southern Min]
-
A.
appliesToLanguageFamily
Indicates that something (such as a rule, feature, or classification) is relevant or applicable to an entire language family rather than to a single language.
-
B.
hasLanguageGroup
Indicates that an entity belongs to, is associated with, or is categorized under a particular language group.
-
C.
appliedToGroupType
Indicates that something (such as a rule, setting, or action) is applied specifically to a particular type or category of group rather than to individual members.
-
D.
appliesTo
chosen
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
E.
languageGroupAttribution
Indicates that an entity is associated with, classified under, or attributed to a particular language group.
- 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_69feecf1bb248190ba30f0bb1d22ee08 |
completed | May 9, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69feea5f27748190b223ee4e3ba5a678 |
completed | May 9, 2026, 8:03 a.m. |
Created at: May 1, 2026, 1:25 a.m.