Triple
T24785221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tadfield |
E620098
|
entity |
| Predicate | hasResidentGroup |
P134232
|
FINISHED |
| Object | the Them |
—
|
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: the Them | Statement: [Tadfield, hasResidentGroup, the Them]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidentGroup Context triple: [Tadfield, hasResidentGroup, the Them]
-
A.
residenceGroup
chosen
Indicates that multiple entities share a common place of residence or are grouped together based on living at the same location.
-
B.
hasResidentOrganization
Indicates that an organization is based in, operates from, or maintains a primary presence within a particular place or facility.
-
C.
hasResidentPopulation
Indicates that a place or administrative area has a population of people who live there permanently or for an extended period.
-
D.
hasNonHumanResident
Indicates that a place or location is inhabited or occupied by one or more non-human entities.
-
E.
hasCommunityGroup
Indicates that an entity is associated with, or belongs to, a specific community group.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 18, 2026, 4:45 a.m.