Triple
T22122029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hartwell House |
E546694
|
entity |
| Predicate | hasGroundsSize |
P34032
|
FINISHED |
| Object | approximately 90 acres |
—
|
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: approximately 90 acres | Statement: [Hartwell House, hasGroundsSize, approximately 90 acres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGroundsSize Context triple: [Hartwell House, hasGroundsSize, approximately 90 acres]
-
A.
hasGrounds
Indicates that one entity possesses or includes a physical area of land or outdoor space associated with it.
-
B.
hasSize
chosen
Indicates that one entity possesses a particular physical magnitude or extent, such as length, volume, or overall dimensions.
-
C.
hasSizeSystem
Indicates that an entity is associated with or defined according to a particular size measurement system.
-
D.
hasRegulationSize
Indicates that something conforms to an officially defined or standard size specified by rules or regulations.
-
E.
hasGroundsLaidOutBy
Indicates that the layout or arrangement of the grounds (e.g., gardens, surrounding land) of one entity was designed or established by 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1297e7e188190873924403421caa2 |
completed | April 28, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.