Triple
T81330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquia Creek sandstone |
E1632
|
entity |
| Predicate | materialOf |
P618
|
FINISHED |
| Object | architectural details of the White House |
—
|
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: architectural details of the White House | Statement: [Aquia Creek sandstone, materialOf, architectural details of the White House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialOf Context triple: [Aquia Creek sandstone, materialOf, architectural details of the White House]
-
A.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
B.
material
chosen
Indicates that one entity is physically composed of, made from, or constructed using the substance or material represented by the other entity.
-
C.
hasMaterialType
Indicates that something is composed of, made from, or characterized by a specific type of material.
-
D.
subjectMatter
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
E.
surfaceType
Indicates the kind or classification of surface associated with an entity or interaction.
- 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a25053ca208190a371b0d38000c2b9 |
completed | Feb. 28, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69a24eb2998c819082681da74601d446 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.