Triple
T27756982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp Toccoa |
E701357
|
entity |
| Predicate | hasStructureRemnant |
P191563
|
FINISHED |
| Object | foundations of original buildings |
—
|
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: foundations of original buildings | Statement: [Camp Toccoa, hasStructureRemnant, foundations of original buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStructureRemnant Context triple: [Camp Toccoa, hasStructureRemnant, foundations of original buildings]
-
A.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
B.
hasKeepStructure
Indicates that one entity possesses or includes a defensive or central keep-like structure as part of its overall form or composition.
-
C.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
-
D.
hasMainStructure
Indicates that one entity serves as the primary or central structural component of another entity.
-
E.
hasHiddenStructure
Indicates that an entity possesses an internal or underlying structure that is not directly visible or apparent.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: April 27, 2026, 4:24 p.m.