Triple
T38447458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadbeams |
E906677
|
entity |
| Predicate | earlyDwelling |
P190759
|
FINISHED |
| Object | Blue Mountains |
—
|
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: Blue Mountains | Statement: [Broadbeams, earlyDwelling, Blue Mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlyDwelling Context triple: [Broadbeams, earlyDwelling, Blue Mountains]
-
A.
houseFounded
Indicates that an entity (such as a house, organization, or lineage) was established or created by another entity or at a specific time.
-
B.
traditionalHomeEnd
Indicates the point or time at which a traditional home, household, or customary domestic arrangement comes to an end.
-
C.
traditionalHomeOf
Indicates that a place is historically or customarily regarded as the primary homeland or origin location of a particular group or culture.
-
D.
house1
Indicates that something is identified or classified as a house or dwelling.
-
E.
earlyHomeVenueFor
Indicates that one entity served as the primary home venue for another entity during an early or initial period of its existence or activity.
- 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fcce7a25848190bdc66efcbc7cae3a |
completed | May 7, 2026, 5:40 p.m. |
Created at: May 3, 2026, 4:31 p.m.