Triple
T26620632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Flores peoples |
E668185
|
entity |
| Predicate | shareLinguisticFeatures |
P114100
|
FINISHED |
| Object | each other |
—
|
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: each other | Statement: [Central Flores peoples, shareLinguisticFeatures, each other]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareLinguisticFeatures Context triple: [Central Flores peoples, shareLinguisticFeatures, each other]
-
A.
hasDialectalFeaturesSharedWith
chosen
Indicates that two language varieties share specific dialectal features or characteristics in common.
-
B.
sharesLinguisticFamilyWith
Indicates that two languages belong to the same linguistic family or branch within a language family.
-
C.
linguisticFeature
Indicates a relationship where a linguistic property, pattern, or characteristic is attributed to or associated with a language-related entity (such as a word, phrase, or text).
-
D.
shareLanguageInfluence
Indicates that two entities affect or shape each other’s language use, development, or characteristics through mutual or shared influence.
-
E.
sharesLanguageWith
Indicates that two entities use at least one common language for communication.
- 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 27, 2026, 2:20 a.m.