Triple
T591106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biltmore Estate |
E17271
|
entity |
| Predicate | currentEstateArea |
P157
|
FINISHED |
| Object | approximately 8,000 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 8,000 acres | Statement: [Biltmore Estate, currentEstateArea, approximately 8,000 acres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentEstateArea Context triple: [Biltmore Estate, currentEstateArea, approximately 8,000 acres]
-
A.
representedArea
Indicates that one entity serves as a representation or depiction of a particular area or region.
-
B.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
C.
area
Indicates that one entity has a measured two-dimensional extent or surface size quantified by another entity.
-
D.
landArea
chosen
Indicates the total surface area of a piece of land associated with an entity, typically measured in standardized units (e.g., square meters, hectares).
-
E.
hasResidentialArea
Indicates that an entity includes, contains, or is associated with an area designated for people to live or reside.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bb8ff0081909cd53d88930e2693 |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cc13988190892ca10bd7ae9f09 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.