Triple
T21461265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Clubfoot |
E529477
|
entity |
| Predicate | hasAccessionNumber |
P135538
|
FINISHED |
| Object | RF 1977-1 |
—
|
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: RF 1977-1 | Statement: [The Clubfoot, hasAccessionNumber, RF 1977-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessionNumber Context triple: [The Clubfoot, hasAccessionNumber, RF 1977-1]
-
A.
accessionType
Indicates the manner or category by which something is acquired, added, or admitted into a collection, system, or status.
-
B.
requiresForAccession
Indicates that one entity must be obtained, completed, or satisfied before another entity can be accessed, entered, or formally joined.
-
C.
accessionMethod
Indicates the process or means by which something is acquired, obtained, or added to a collection or system.
-
D.
changeOnAccession
Indicates that one entity undergoes a change or update when another entity is newly added, introduced, or comes into effect.
-
E.
hasDesignationNumber
chosen
Indicates that an entity is associated with a specific official designation or identification number.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9ef0c0881908554977df00604a6 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:09 p.m.