Triple
T34107699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Belle Grove |
E874750
|
entity |
| Predicate | propertyInvolved |
P97440
|
FINISHED |
| Object | Belle Grove Plantation |
—
|
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: Belle Grove Plantation | Statement: [Battle of Belle Grove, propertyInvolved, Belle Grove Plantation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyInvolved Context triple: [Battle of Belle Grove, propertyInvolved, Belle Grove Plantation]
-
A.
houseInvolved
Indicates that a house plays a significant role or is directly implicated in the specified event, situation, or relationship.
-
B.
property
Indicates that one entity possesses, is characterized by, or has an attribute or quality associated with another entity.
-
C.
buildingInvolved
chosen
Indicates that a particular building participates in, is affected by, or is otherwise relevant to the specified event or relationship.
-
D.
propertyHeld
Indicates that a particular property is possessed, owned, or controlled by a specified entity.
-
E.
propertySystem
Indicates that one entity functions as a property or attribute system governing or organizing the properties of another entity.
- 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 1:53 a.m.