Triple
T35933912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackmans Swamp |
E1039241
|
entity |
| Predicate | associatedWithColonialEra |
P206109
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Blackmans Swamp, associatedWithColonialEra, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithColonialEra Context triple: [Blackmans Swamp, associatedWithColonialEra, yes]
-
A.
foundedInColonialEra
Indicates that the entity was established or came into existence during a historical period of colonial rule.
-
B.
functionDuringColonialEra
Indicates that the function, role, or activity occurred or was in effect during the colonial era.
-
C.
usedInColonialPeriod
Indicates that something was utilized or in active use during a historical colonial period.
-
D.
associatedWithColonialAdministration
Indicates a relationship where an entity is connected to, involved in, or functioning as part of a colonial administrative system or authority.
-
E.
colonialEraClassification
Indicates how entities are categorized or labeled according to systems or standards established during a colonial historical period.
- F. None of above. chosen
Provenance (4 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037ce53de881908cf14141cf3bc570 |
completed | May 12, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:07 p.m.