Triple
T23906396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London After Midnight |
E601207
|
entity |
| Predicate | leadActorNicknameHolder |
P154039
|
FINISHED |
| Object | Lon Chaney |
—
|
NE NERFINISHED |
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: Lon Chaney | Statement: [London After Midnight, leadActorNicknameHolder, Lon Chaney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadActorNicknameHolder Context triple: [London After Midnight, leadActorNicknameHolder, Lon Chaney]
-
A.
leadCharacterNickname
Indicates that one entity is the nickname commonly used for the lead (main) character of another entity.
-
B.
leadActorCurrentName
Indicates the current, primary name of the actor who plays the leading role in a work.
-
C.
leadActorRolePattern
Indicates a recurring or characteristic type of role that an actor typically plays as a leading performer in productions.
-
D.
leadActorNominee
Indicates that an entity was nominated for a lead acting role in relation to a particular work or award.
-
E.
leadActorOfAdaptation
Indicates that a person is the main actor in a specific adaptation of a work (such as a film, series, or stage version).
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce91144c8190b894e25a45dfd7c9 |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 8:35 p.m.