Triple
T1684087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middleton Place |
E36402
|
entity |
| Predicate | ElizasHouseFunction |
P32724
|
FINISHED |
| Object | interpretive site on slavery and freedpeople |
—
|
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: interpretive site on slavery and freedpeople | Statement: [Middleton Place, ElizasHouseFunction, interpretive site on slavery and freedpeople]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ElizasHouseFunction Context triple: [Middleton Place, ElizasHouseFunction, interpretive site on slavery and freedpeople]
-
A.
houseLocatedIn
Indicates that a house is situated within or belongs to a specific geographic location or area.
-
B.
house1
Indicates that something is identified or classified as a house or dwelling.
-
C.
house2
Indicates a relationship where one entity is a secondary, related, or alternative house associated with another entity.
-
D.
houseFounded
Indicates that an entity (such as a house, organization, or lineage) was established or created by another entity or at a specific time.
-
E.
hasHouse
Indicates that one entity possesses, owns, or is provided with a house in relation to another entity.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aba644070c81908745b56d981fe273 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61b57a6881909373af287ef24799 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69aba641e6a881909645577e72b53df2 |
completed | March 7, 2026, 4:14 a.m. |
Created at: March 4, 2026, 7:29 p.m.