Triple
T26487278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaisigano |
E664855
|
entity |
| Predicate | usesTraditionalSystem |
P164841
|
FINISHED |
| Object | faamatai (chiefly system) |
—
|
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: faamatai (chiefly system) | Statement: [Vaisigano, usesTraditionalSystem, faamatai (chiefly system)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTraditionalSystem Context triple: [Vaisigano, usesTraditionalSystem, faamatai (chiefly system)]
-
A.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
-
B.
isTraditionalInCountry
Indicates that something is customary, long-established, or commonly practiced within a particular country.
-
C.
usesTraditionalDecoration
Indicates that an entity employs customary or historically established decorative styles or motifs in its design or presentation.
-
D.
hasTraditionalFeatures
Indicates that something possesses characteristics or attributes commonly associated with established traditions or customary practices.
-
E.
settingTraditional
Indicates that something is situated or occurs within a traditional setting, context, or environment.
- F. None of above. chosen
Provenance (4 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f650fc44e48190bc0e0a935eac62a6 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f650c466b881908954e43bfebae8a4 |
completed | May 2, 2026, 7:30 p.m. |
Created at: April 27, 2026, 12:31 a.m.