Triple
T30669494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawiyah |
E780754
|
entity |
| Predicate | hasResidentialAreaFor |
P9064
|
FINISHED |
| Object | plant employees |
—
|
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: plant employees | Statement: [Hawiyah, hasResidentialAreaFor, plant employees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidentialAreaFor Context triple: [Hawiyah, hasResidentialAreaFor, plant employees]
-
A.
hasResidentialArea
chosen
Indicates that an entity includes, contains, or is associated with an area designated for people to live or reside.
-
B.
isResidentialBaseFor
Indicates that a location serves as the primary place of residence or home base for a person or group.
-
C.
hasResidentialBuilding
Indicates that an entity possesses, contains, or is associated with a residential building as part of its properties or components.
-
D.
isInResidentialArea
Indicates that something is located within a residential area, such as a neighborhood or zone primarily designated for housing.
-
E.
isResidentialRegionPart
Indicates that one residential region is a constituent or included part of another, larger residential region.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00a094c44c81908e4501151688a635 |
completed | May 10, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_6a009fcdfd848190841deaad9667d347 |
completed | May 10, 2026, 3:10 p.m. |
Created at: April 29, 2026, 8:31 p.m.