Triple
T37777212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enxaimel (half-timbered) style |
E941719
|
entity |
| Predicate | loadBearingElement |
P71822
|
FINISHED |
| Object | wooden posts and beams |
—
|
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: wooden posts and beams | Statement: [Enxaimel (half-timbered) style, loadBearingElement, wooden posts and beams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loadBearingElement Context triple: [Enxaimel (half-timbered) style, loadBearingElement, wooden posts and beams]
-
A.
loadBearingFor
chosen
Indicates that one entity structurally supports and carries the weight or load of another entity.
-
B.
canBeBorneBy
Indicates that one entity is capable of being carried, supported, or transported by another entity.
-
C.
axleLoad
Indicates the amount of weight or force that is supported or exerted by a single axle in a vehicle or structure.
-
D.
weightSupport
Indicates that one entity bears or carries the physical weight of another, providing structural or mechanical support.
-
E.
slingLoadCapacity
Indicates the maximum weight or load that can be safely carried or supported using a sling.
- 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbaf443e5c8190bfaf3e00ced78a30 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:19 p.m.