Triple
T31235893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Charles Baskerville |
E796420
|
entity |
| Predicate | footprintsFoundNearBody |
P171368
|
FINISHED |
| Object | gigantic hound |
—
|
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: gigantic hound | Statement: [Sir Charles Baskerville, footprintsFoundNearBody, gigantic hound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: footprintsFoundNearBody Context triple: [Sir Charles Baskerville, footprintsFoundNearBody, gigantic hound]
-
A.
discoveredOnBody
Indicates that something (such as an item, mark, or substance) was found on the surface or person of a body.
-
B.
discoveredOnBodyBy
Indicates that a body was discovered by a particular person or agent.
-
C.
performedOnFoot
Indicates that an action or activity was carried out while walking or traveling on foot rather than using a vehicle or other means of transport.
-
D.
locatedOnBody
Indicates that one entity is physically situated on the surface or external part of another entity’s body.
-
E.
hasFootUsed
Indicates that an entity uses a particular foot (or feet) to perform an action or function.
- 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_69f224db69ac81909a370adad6a7ac7c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69dfbf6ac8190ba2e6fc0adfd8b73 |
completed | May 3, 2026, 12:59 a.m. |
Created at: April 29, 2026, 9:11 p.m.