Triple
T4430800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grotte de Mas d’Azil |
E95322
|
entity |
| Predicate | hasFinding |
P25771
|
FINISHED |
| Object | painted pebbles |
—
|
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: painted pebbles | Statement: [Grotte de Mas d’Azil, hasFinding, painted pebbles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinding Context triple: [Grotte de Mas d’Azil, hasFinding, painted pebbles]
-
A.
containsFinding
chosen
Indicates that one entity includes, encompasses, or holds a particular finding as part of its content or results.
-
B.
finds
Indicates that one entity discovers, locates, or comes upon another entity, often as the result of a search or encounter.
-
C.
hasResearchFinding
Indicates that an entity has produced, contains, or is associated with a specific research finding or result.
-
D.
requiresFinding
Indicates that one entity’s validity, execution, or completion is contingent upon a specific finding or determination being made about another entity.
-
E.
supportsFinding
Indicates that one entity provides the capability or functionality needed to perform, enable, or carry out a particular finding operation on another entity or resource.
- 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3556b71448190a3fab938853f8b87 |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:31 p.m.