Triple
T4569185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Desperado |
E122986
|
entity |
| Predicate | rcdbNumber |
P26175
|
FINISHED |
| Object | 72 |
—
|
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: 72 | Statement: [Desperado, rcdbNumber, 72]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rcdbNumber Context triple: [Desperado, rcdbNumber, 72]
-
A.
ISONumber
Indicates that an entity is associated with, identified by, or conforms to a specific ISO (International Organization for Standardization) number or standard.
-
B.
censusNumber
Indicates the unique identifier or count assigned to an entity within an official census record.
-
C.
refnum
chosen
Indicates that an entity is associated with a specific reference number used to identify or track it.
-
D.
cabinetNumberInHistory
Indicates the specific cabinet number assigned to an entity within a historical record or context.
-
E.
regimentalNumber
Indicates the unique identifying number assigned to a member of a regiment, linking an individual to their specific regimental record.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58a0dfbc81909b5023f0c29addaf |
completed | March 20, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.