Triple
T487076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appomattox Court House, Virginia |
E9900
|
entity |
| Predicate | buildingMaterialTypical |
P1272
|
FINISHED |
| Object | wood-frame construction |
—
|
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: wood-frame construction | Statement: [Appomattox Court House, Virginia, buildingMaterialTypical, wood-frame construction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingMaterialTypical Context triple: [Appomattox Court House, Virginia, buildingMaterialTypical, wood-frame construction]
-
A.
constructionType
Indicates the specific method or style by which something is built or constructed.
-
B.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
C.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
D.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
E.
typicalProductionType
Indicates the usual or characteristic type of production activity associated with an 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0de66308190a18503a482881cfc |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf63fbc819090ea6ca11f39116a |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.