Triple
T7967365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project 23 |
E185238
|
entity |
| Predicate | excavationSiteType |
P40905
|
FINISHED |
| Object | asphaltic fossil deposit |
—
|
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: asphaltic fossil deposit | Statement: [Project 23, excavationSiteType, asphaltic fossil deposit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excavationSiteType Context triple: [Project 23, excavationSiteType, asphaltic fossil deposit]
-
A.
excavationSite
Indicates a location where digging or removal of earth or materials is actively conducted, typically for construction, mining, or archaeological purposes.
-
B.
excavationType
Indicates the specific method or category of excavation associated with an entity or activity.
-
C.
hasArchaeologicalSiteType
Indicates that an entity is classified as, or associated with, a specific type or category of archaeological site.
-
D.
fossilSiteType
chosen
Indicates the specific type or classification of a site where fossils are found or collected.
-
E.
excavationPurpose
Indicates that an excavation is carried out with a specific intended purpose or objective.
- 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ba3f53c8190a0e9b3de2f1b9645 |
completed | March 31, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69cb047a8e4c81909b79e0f0bf56440c |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:13 p.m.