Triple
T3490223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenterfield |
E73709
|
entity |
| Predicate | hasBuiltEnvironmentType |
P11679
|
FINISHED |
| Object | Victorian-era architecture |
—
|
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: Victorian-era architecture | Statement: [Tenterfield, hasBuiltEnvironmentType, Victorian-era architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuiltEnvironmentType Context triple: [Tenterfield, hasBuiltEnvironmentType, Victorian-era architecture]
-
A.
hasBuiltEnvironment
chosen
Indicates that an entity possesses, contains, or is associated with human-made physical structures or infrastructure in its environment.
-
B.
hasEnvironmentType
Indicates that an entity is associated with or occurs within a specific type or category of environment.
-
C.
hasBuilt
Indicates that one entity is the creator or constructor of another entity.
-
D.
hasEnvironmentalFunction
Indicates that an entity serves a specific role or purpose related to the environment, such as contributing to ecological processes, protection, or sustainability.
-
E.
hasProjectType
Indicates that an entity is associated with, or classified under, a specific type or category of project.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbb94190c8190a81eb41042e51a00 |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0b34908190b2bb5766a2231f7a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.