Triple
T24945968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kulin peoples |
E624185
|
entity |
| Predicate | sharesLanguageFeaturesWith |
P114100
|
FINISHED |
| Object | Wurundjeri people |
—
|
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: Wurundjeri people | Statement: [Kulin peoples, sharesLanguageFeaturesWith, Wurundjeri people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesLanguageFeaturesWith Context triple: [Kulin peoples, sharesLanguageFeaturesWith, Wurundjeri people]
-
A.
sharesLanguageWith
Indicates that two entities use at least one common language for communication.
-
B.
hasDialectalFeaturesSharedWith
chosen
Indicates that two language varieties share specific dialectal features or characteristics in common.
-
C.
shareLanguageInfluence
Indicates that two entities affect or shape each other’s language use, development, or characteristics through mutual or shared influence.
-
D.
sharesLinguisticFamilyWith
Indicates that two languages belong to the same linguistic family or branch within a language family.
-
E.
sharesSpellingWith
Indicates that two entities have identical or substantially identical written forms (i.e., they are spelled the same way).
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 18, 2026, 5:54 a.m.