Triple
T81333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquia Creek sandstone |
E1632
|
entity |
| Predicate | sourceFor |
P409
|
FINISHED |
| Object | historic quarries in Stafford County |
—
|
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: historic quarries in Stafford County | Statement: [Aquia Creek sandstone, sourceFor, historic quarries in Stafford County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceFor Context triple: [Aquia Creek sandstone, sourceFor, historic quarries in Stafford County]
-
A.
source
chosen
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
B.
primarySources
Indicates that one entity serves as an original, authoritative source of information or evidence for another entity.
-
C.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
-
D.
sourceRegion
Indicates the geographic or spatial region from which something originates or is derived.
-
E.
languageOfSources
Indicates that the specified language is the language in which the referenced sources or source materials are expressed.
- 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.