Triple
T31706043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Adventure of the Reigate Squire |
E809182
|
entity |
| Predicate | keyClue |
P172451
|
FINISHED |
| Object | torn piece of a note |
—
|
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: torn piece of a note | Statement: [The Adventure of the Reigate Squire, keyClue, torn piece of a note]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyClue Context triple: [The Adventure of the Reigate Squire, keyClue, torn piece of a note]
-
A.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
B.
keys
Indicates that one entity serves as a key (or set of keys) that can open, access, or control another entity.
-
C.
keyExample
Indicates that something serves as a representative or illustrative instance of a key concept, feature, or case.
-
D.
keyTown
Indicates that a town holds strategic, administrative, or economic importance within a larger region or system.
-
E.
keyComponent
Indicates that one entity is an essential or foundational part required for the proper function, structure, or identity of 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:13 p.m.