Triple
T36179283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Fort |
E1046664
|
entity |
| Predicate | hasEmbrasures |
P6684
|
FINISHED |
| Object | gun ports for artillery |
—
|
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: gun ports for artillery | Statement: [Star Fort, hasEmbrasures, gun ports for artillery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmbrasures Context triple: [Star Fort, hasEmbrasures, gun ports for artillery]
-
A.
hasArchedEntrances
Indicates that an entity features one or more entrances constructed with an arched shape.
-
B.
hasSerrations
Indicates that one entity possesses serrated or saw-like edges, surfaces, or features.
-
C.
hasBalustrades
Indicates that one entity features or is equipped with balustrades as part of its structure or design.
-
D.
hasArchitecturalFeature
chosen
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
E.
hasCornice
Indicates that one entity (typically a building or structure) possesses a cornice as an architectural feature.
- 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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:08 p.m.