Triple
T5794869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swartkrans |
E128483
|
entity |
| Predicate | hasPreservationType |
P66565
|
FINISHED |
| Object | cave infill |
—
|
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: cave infill | Statement: [Swartkrans, hasPreservationType, cave infill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreservationType Context triple: [Swartkrans, hasPreservationType, cave infill]
-
A.
hasParType
Indicates that an entity has a specific parent type or category to which it belongs.
-
B.
hasContentType
Indicates that an entity is associated with or classified by a specific type of content.
-
C.
hasSerialization
Indicates that one entity is represented, encoded, or stored as a serialized form in another entity.
-
D.
hasBinary
Indicates that one entity is associated with another entity in a binary (two-component) relationship, typically as one of the two members of a pair.
-
E.
hasPropertyType
Indicates that an entity possesses or is associated with a specific type or category of property.
- 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_69c00845ca68819081a2ce3ecca577f7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1304588190b59a18fb7b70a60f |
completed | March 22, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69c021d477008190946113f9859eeb90 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c02b10def8819080859bc6505405ed |
completed | March 22, 2026, 5:46 p.m. |
Created at: March 22, 2026, 3:51 p.m.