Triple
T27632298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Follies (architecture) |
E696368
|
entity |
| Predicate | oftenBuiltBy |
P175634
|
FINISHED |
| Object | aristocratic landowners |
—
|
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: aristocratic landowners | Statement: [Follies (architecture), oftenBuiltBy, aristocratic landowners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenBuiltBy Context triple: [Follies (architecture), oftenBuiltBy, aristocratic landowners]
-
A.
originallyBuiltBy
Indicates that something was first constructed or created by a particular agent, organization, or entity.
-
B.
builtInThe
Indicates that something was constructed or created within a specified location, structure, or context.
-
C.
builtUpBy
Indicates that something has been constructed, developed, or formed through the actions or contributions of a specified agent or process.
-
D.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
E.
engineeredBy
Indicates that an entity has been designed, created, or developed through the technical work or expertise of another entity.
- F. None of above. chosen
Provenance (4 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_69ef59092c8881908114ad184248cc46 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: April 27, 2026, 2:21 p.m.