Triple
T13557560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lignumvitae Key Botanical State Park |
E323813
|
entity |
| Predicate | MathesonHouseBuiltIn |
P18074
|
FINISHED |
| Object | 1919 |
—
|
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: 1919 | Statement: [Lignumvitae Key Botanical State Park, MathesonHouseBuiltIn, 1919]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MathesonHouseBuiltIn Context triple: [Lignumvitae Key Botanical State Park, MathesonHouseBuiltIn, 1919]
-
A.
houseProduced
Indicates that a house or housing unit was created, built, or generated by a particular agent, process, or source.
-
B.
glassHouseInspiredBy
Indicates that the design, concept, or creation of a glass house is influenced or derived from another work, style, or source.
-
C.
modernHomeSymbolizes
Indicates that a modern home serves as a symbol or representation of a particular idea, value, or concept.
-
D.
buildingSystem
Indicates that one entity functions as a system, subsystem, or organized set of components that serves or supports the operation of a building.
-
E.
houseFounded
chosen
Indicates that an entity (such as a house, organization, or lineage) was established or created by another entity or at a specific time.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae13bec4819084c1770638c00ed9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:47 p.m.