Triple
T31329821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lakkoi quarries |
E798992
|
entity |
| Predicate | extractionTechnique |
P92403
|
FINISHED |
| Object | ancient open-pit quarrying |
—
|
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: ancient open-pit quarrying | Statement: [Lakkoi quarries, extractionTechnique, ancient open-pit quarrying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extractionTechnique Context triple: [Lakkoi quarries, extractionTechnique, ancient open-pit quarrying]
-
A.
overseesExtractionOf
Indicates that one entity supervises, manages, or has responsibility for the process by which another entity is extracted or obtained.
-
B.
oilExtractionMethod
Indicates the technique or process used to extract oil from a source.
-
C.
extractedIn
Indicates that one entity is obtained, derived, or separated from another entity through an extraction process.
-
D.
featuresTechnique
Indicates that something incorporates or makes use of a particular technique as part of its content or execution.
-
E.
hasExtractionType
chosen
Indicates that one entity is associated with a specific method, category, or mode by which something is extracted from it or through it.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edf9bb0819086c9cf57538b4d0a |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:16 p.m.