Triple
T22394698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Who Am I? (Les Misérables song) |
E553598
|
entity |
| Predicate | identifiesCharacterByNumber |
P138880
|
FINISHED |
| Object | 24601 |
—
|
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: 24601 | Statement: [Who Am I? (Les Misérables song), identifiesCharacterByNumber, 24601]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiesCharacterByNumber Context triple: [Who Am I? (Les Misérables song), identifiesCharacterByNumber, 24601]
-
A.
screenCharacterBy
Indicates a relationship where one entity evaluates or selects characters according to certain criteria or standards.
-
B.
representedByCharacter
Indicates that one entity is depicted, symbolized, or personified by a particular character in a work or medium.
-
C.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
D.
mainCharacterCodeNumber
chosen
Indicates that an entity is identified as the primary or central character by a specific code number.
-
E.
characterCorrespondsTo
Indicates that one character is equivalent to, maps onto, or represents another character in a defined correspondence or mapping.
- 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1585dac3c8190bc221f35b3eefa3f |
completed | April 29, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.