Triple
T21134560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Brown (The Taking of Pelham One Two Three) |
E520781
|
entity |
| Predicate | usesAliasFormat |
P139276
|
FINISHED |
| Object | color plus surname |
—
|
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: color plus surname | Statement: [Mr. Brown (The Taking of Pelham One Two Three), usesAliasFormat, color plus surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAliasFormat Context triple: [Mr. Brown (The Taking of Pelham One Two Three), usesAliasFormat, color plus surname]
-
A.
usesAliasFor
Indicates that one entity employs an alternative name or identifier to refer to another entity.
-
B.
usesAliasConvention
chosen
Indicates that one entity adopts or follows a specific alias-naming convention when referring to another entity.
-
C.
usesAliasTo
Indicates that one entity employs an alternative name or identifier to refer to or represent another entity.
-
D.
usedByAlias
Indicates that something is utilized, referenced, or accessed through an alternative name or alias.
-
E.
usesAliasTheme
Indicates that one entity adopts or operates under an alternative thematic identity or label associated with another entity.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723592fd48190ba5977a1b229d51e |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.