Triple
T37706258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stonehenge Phase I ditch and bank |
E939205
|
entity |
| Predicate | materialExtractedAs |
P10922
|
FINISHED |
| Object | chalk |
—
|
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: chalk | Statement: [Stonehenge Phase I ditch and bank, materialExtractedAs, chalk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialExtractedAs Context triple: [Stonehenge Phase I ditch and bank, materialExtractedAs, chalk]
-
A.
materialFormedIn
Indicates that a material is created, produced, or formed within a specified process, environment, or context.
-
B.
extractedIn
Indicates that one entity is obtained, derived, or separated from another entity through an extraction process.
-
C.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
D.
resourceExtracted
chosen
Indicates that a resource has been obtained or taken from a source entity, typically through an extraction process.
-
E.
materialSource
Indicates that one entity serves as the origin or provider of the material or substance used by another entity.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:18 p.m.