Triple
T36744348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bree |
E907710
|
entity |
| Predicate | hasInhabitantsCalled |
P197844
|
FINISHED |
| Object | Bree-landers |
—
|
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: Bree-landers | Statement: [Bree, hasInhabitantsCalled, Bree-landers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInhabitantsCalled Context triple: [Bree, hasInhabitantsCalled, Bree-landers]
-
A.
hasInhabitantName
chosen
Indicates that a place or region is associated with the specific name used for its inhabitants (demonym).
-
B.
hasInhabitantsCharacteristic
Indicates that a place or region is associated with a particular characteristic, quality, or attribute of its inhabitants.
-
C.
hasCall
Indicates that one entity initiates or participates in a telephone or voice communication with another entity.
-
D.
membersCalled
Indicates that specific members of a group or collection are being referred to or identified by a particular name or label.
-
E.
refersToInhabitantsOfType
Indicates that something is referring specifically to inhabitants belonging to a particular type or category.
- 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_69f76e76d10881909ec1679bc043108c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00be8ee4bc8190b795d9606f0e490c |
completed | May 10, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_6a00bde163c88190867104bd08cac2ee |
completed | May 10, 2026, 5:18 p.m. |
Created at: May 3, 2026, 4:12 p.m.