Triple
T24945976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kulin peoples |
E624185
|
entity |
| Predicate | usesMoietySystem |
P72601
|
FINISHED |
| Object | Bunjil moiety |
—
|
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: Bunjil moiety | Statement: [Kulin peoples, usesMoietySystem, Bunjil moiety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMoietySystem Context triple: [Kulin peoples, usesMoietySystem, Bunjil moiety]
-
A.
moietySystem
chosen
Indicates a relationship where an entity is classified or organized according to a moiety system, typically dividing a society or group into two complementary social halves.
-
B.
usesMolecule
Indicates that one entity employs or utilizes a particular molecule in performing an action, process, or function.
-
C.
isMonoisotopic
Indicates that something consists of or relates to only a single isotope, without isotopic variation.
-
D.
hasProportionSystem
Indicates that one entity possesses or is characterized by a particular system for managing or defining proportions or ratios.
-
E.
usedWithSubunit
Indicates that one entity is employed, operated, or functions in conjunction with a specific subunit of another entity.
- 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_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 5:54 a.m.