Triple
T27960247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrowtown |
E704557
|
entity |
| Predicate | ChineseSettlementBuiltFor |
P164368
|
FINISHED |
| Object | Chinese gold miners |
—
|
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: Chinese gold miners | Statement: [Arrowtown, ChineseSettlementBuiltFor, Chinese gold miners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ChineseSettlementBuiltFor Context triple: [Arrowtown, ChineseSettlementBuiltFor, Chinese gold miners]
-
A.
traditionalSettlement
Indicates that an entity is a settlement characterized by long-established, customary, or historically rooted patterns of habitation and land use.
-
B.
inspiredSettlement
Indicates that one entity’s ideas, actions, or example motivated or influenced the creation, development, or characteristics of a particular settlement.
-
C.
originOfSettlement
Indicates the place, source, or starting point from which a settlement was established or originated.
-
D.
placeBuilt
Indicates that a structure or facility was constructed at a specific location.
-
E.
originalSettlement
Indicates that one entity is the initial or first-established settlement location associated with another entity.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 7:31 p.m.