Triple
T4383090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephen King House |
E99174
|
entity |
| Predicate | hasFence |
P14204
|
FINISHED |
| Object | ornate iron gate with bat designs |
—
|
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: ornate iron gate with bat designs | Statement: [Stephen King House, hasFence, ornate iron gate with bat designs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFence Context triple: [Stephen King House, hasFence, ornate iron gate with bat designs]
-
A.
hasBorderWallOrFence
chosen
Indicates that a physical barrier such as a wall or fence exists along the border between two entities.
-
B.
hasFaregates
Indicates that an entity is equipped with or contains faregates used to control or validate access, typically for paid entry.
-
C.
numberOfFences
Indicates the quantity of fences associated with or present around a given entity.
-
D.
hasBoundaryFeature
Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
-
E.
hasGate
Indicates that one entity possesses, includes, or is equipped with a gate as part of its structure or configuration.
- 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_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35262649c8190a724c9835cb7ece6 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:18 p.m.