Triple
T3853919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grotte de Niaux |
E85363
|
entity |
| Predicate | hasFloorMarkings |
P51959
|
FINISHED |
| Object | traces of prehistoric footprints |
—
|
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: traces of prehistoric footprints | Statement: [Grotte de Niaux, hasFloorMarkings, traces of prehistoric footprints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloorMarkings Context triple: [Grotte de Niaux, hasFloorMarkings, traces of prehistoric footprints]
-
A.
hasFloorColor
Indicates that an entity possesses a floor whose surface is characterized by a specific color.
-
B.
hasFloorMaterial
Indicates that an entity’s floor is made of, covered with, or constructed from a specified material.
-
C.
hasFloor
Indicates that one entity possesses, includes, or is associated with a particular floor or level within a structure.
-
D.
hasRunwayMarkings
Indicates that a runway possesses specific painted markings or symbols on its surface.
-
E.
hasFlooring
Indicates that one entity is equipped with or covered by a particular type of flooring material provided by another entity.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec0438308190865ff74bee5a1cf2 |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee8d9b328819080158be59e5bcc97 |
completed | March 9, 2026, 3:35 p.m. |
Created at: March 9, 2026, 3:19 p.m.