Triple
T9733154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antique rice terraces |
E235993
|
entity |
| Predicate | builtEnvironmentType |
P853
|
FINISHED |
| Object | rural landscape |
—
|
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: rural landscape | Statement: [Antique rice terraces, builtEnvironmentType, rural landscape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtEnvironmentType Context triple: [Antique rice terraces, builtEnvironmentType, rural landscape]
-
A.
builtEnvironment
Indicates that something is part of, related to, or characteristic of human-made physical surroundings such as buildings, infrastructure, and other constructed spaces.
-
B.
environmentType
chosen
Indicates the kind or category of environment associated with an entity or situation.
-
C.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
D.
buildingSystem
Indicates that one entity functions as a system, subsystem, or organized set of components that serves or supports the operation of a building.
-
E.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9eb54fe481908b0202f104b75dc1 |
completed | April 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:22 p.m.