Triple
T30724246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perlisian |
E782234
|
entity |
| Predicate | usesAdjectivalForm |
P64799
|
FINISHED |
| Object | Perlisian (as adjective for things from Perlis) |
—
|
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: Perlisian (as adjective for things from Perlis) | Statement: [Perlisian, usesAdjectivalForm, Perlisian (as adjective for things from Perlis)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAdjectivalForm Context triple: [Perlisian, usesAdjectivalForm, Perlisian (as adjective for things from Perlis)]
-
A.
hasAdjectiveForm
chosen
Indicates that one term is the adjective form derived from another related term (such as a noun or verb).
-
B.
hasAdjectiveEnding
Indicates that something possesses or is marked by a particular adjective-like ending or suffix.
-
C.
hasAdverb
Indicates that an action, event, or state is modified or described by an adverb.
-
D.
usesAffixation
Indicates that one entity forms or modifies another by adding affixes (such as prefixes, suffixes, infixes, or circumfixes) to it.
-
E.
hasAdjectiveDeclensionType
Indicates that an adjective is associated with a specific pattern or type of grammatical declension.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 29, 2026, 8:36 p.m.