Triple
T34325760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lutruwita |
E880859
|
entity |
| Predicate | hasModernColonialName |
P13172
|
FINISHED |
| Object | Tasmania |
—
|
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: Tasmania | Statement: [lutruwita, hasModernColonialName, Tasmania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernColonialName Context triple: [lutruwita, hasModernColonialName, Tasmania]
-
A.
hasModernName
Indicates that an entity is associated with its current or contemporary name, as opposed to an older or historical one.
-
B.
hasColonialName
chosen
Indicates that an entity is known by, or has been assigned, a name originating from a colonial power or colonial period.
-
C.
hasModernHistoriographicalName
Indicates that an entity is associated with the name or label used for it in modern historiography.
-
D.
hasModernNamesake
Indicates that an entity is the namesake or inspiration for a modern entity that shares or derives its name from it.
-
E.
preColonialNameFor
Indicates that one name was used for something in the pre-colonial period and refers to the same entity later known by a different (typically colonial or post-colonial) name.
- 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_69f349b9cd508190a996a616903b3e6d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: May 1, 2026, 1:58 a.m.