Triple
T4529449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit Red |
E106258
|
entity |
| Predicate | identityRelation |
P57270
|
FINISHED |
| Object | earlier identity of Malcolm X |
—
|
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: earlier identity of Malcolm X | Statement: [Detroit Red, identityRelation, earlier identity of Malcolm X]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identityRelation Context triple: [Detroit Red, identityRelation, earlier identity of Malcolm X]
-
A.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
B.
valueRelation
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
-
C.
termRelationTo
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
-
D.
titleRelation
Indicates a relationship where one entity serves as the title, designation, or formal name associated with another entity.
-
E.
semanticRelation
Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd579ba4188190b4cef6e91772f7e5 |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521cf77c819083852de3094d1377 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:03 p.m.