Triple
T20994504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bev |
E517110
|
entity |
| Predicate | houseSaleTriggers |
P142401
|
FINISHED |
| Object | conflict among neighbors |
—
|
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: conflict among neighbors | Statement: [Bev, houseSaleTriggers, conflict among neighbors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseSaleTriggers Context triple: [Bev, houseSaleTriggers, conflict among neighbors]
-
A.
soldPropertyFor
Indicates that one entity transferred ownership of a property to another entity in exchange for a specified amount of money or value.
-
B.
soldProperty
Indicates that one entity transferred ownership of a property to another entity in exchange for payment.
-
C.
houseResult
Indicates the outcome or status produced by a housing-related process, event, or decision involving the referenced entities.
-
D.
realEstate
Indicates a relationship where an entity owns, manages, or is otherwise associated with real property such as land or buildings.
-
E.
openHouseHeld
Indicates that an open house event was conducted or hosted for a particular property or location.
- 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc1e75188190a97114238ea0b4f9 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:50 p.m.