Triple
T2066024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedford limestone |
E45901
|
entity |
| Predicate | wasExtensivelyUsedIn |
P11801
|
FINISHED |
| Object | early 20th century American 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: early 20th century American architecture | Statement: [Bedford limestone, wasExtensivelyUsedIn, early 20th century American architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasExtensivelyUsedIn Context triple: [Bedford limestone, wasExtensivelyUsedIn, early 20th century American architecture]
-
A.
wasUsedBy
Indicates that something served as a tool, resource, or means for an agent to perform an action or achieve a result.
-
B.
widelyUsedIn
chosen
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
C.
alsoUsedIn
Indicates that something is additionally employed, applied, or present in another context, setting, or use case beyond the primary one.
-
D.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
E.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
- 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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9f0cb888190a97884f5a722d91f |
completed | March 7, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69abb7aee9b48190999620176e3a6ee2 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:40 p.m.