Triple
T1004294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquia Creek area |
E21673
|
entity |
| Predicate | quarriedFor |
P22209
|
FINISHED |
| Object | building stone |
—
|
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: building stone | Statement: [Aquia Creek area, quarriedFor, building stone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quarriedFor Context triple: [Aquia Creek area, quarriedFor, building stone]
-
A.
quarriedNear
Indicates that a material or resource was extracted from a quarry located close to a specified place or feature.
-
B.
excavatedBy
Indicates that something (typically an archaeological site, artifact, or geological feature) was uncovered or dug out by a particular agent (such as a person, team, or organization).
-
C.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
D.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
E.
stateGemstone
Indicates a relationship where a state is officially associated with or designated a particular gemstone.
- 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4ff614081909478500ada1f5059 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b1f4f88190822598cfd2a0fd2b |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b36064a48190b85c402f32cbadd1 |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:41 p.m.