Triple
T15060725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woppaburra |
E379616
|
entity |
| Predicate | hasClanTotem |
P116140
|
FINISHED |
| Object | Various marine species (including turtles and fish) |
—
|
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: Various marine species (including turtles and fish) | Statement: [Woppaburra, hasClanTotem, Various marine species (including turtles and fish)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClanTotem Context triple: [Woppaburra, hasClanTotem, Various marine species (including turtles and fish)]
-
A.
hasTotem
chosen
Indicates that one entity possesses, is symbolically represented by, or is associated with another entity as its totem.
-
B.
hasClanSeat
Indicates that an entity holds an official seat or position within a particular clan.
-
C.
hasClanTerritory
Indicates that a clan possesses or controls a specific geographic territory as its domain.
-
D.
clanCrestAssociatedWith
Indicates that a particular clan crest is symbolically or traditionally linked to a specific clan or family.
-
E.
hasClanStatus
Indicates that an entity holds a specific role, rank, or membership status within a clan or clan-like group.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dedee6a55c8190b40c4672fb46b79b |
completed | April 15, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:01 a.m.