Triple
T28018619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sullivan’s Island (1776) |
E707621
|
entity |
| Predicate | fortMaterial |
P65657
|
FINISHED |
| Object | palmetto log fortifications |
—
|
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: palmetto log fortifications | Statement: [Battle of Sullivan’s Island (1776), fortMaterial, palmetto log fortifications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortMaterial Context triple: [Battle of Sullivan’s Island (1776), fortMaterial, palmetto log fortifications]
-
A.
fortType
Indicates the specific kind or classification of a fort associated with an entity.
-
B.
materialOfFortifications
chosen
Indicates that a specified material is used in the construction or composition of certain fortifications.
-
C.
foundationMaterial
Indicates the material from which the foundation or base of something is constructed.
-
D.
مادة البناء
Indicates a relationship where something serves as, or is used as, a construction material in building or structural work.
-
E.
isFortifiedWith
Indicates that one entity has been strengthened, enriched, or supplemented by the addition of 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c09382c81909819e586594cd93a |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:08 p.m.