Triple
T29077272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X-23 |
E735975
|
entity |
| Predicate | relationshipToWolverine |
P202780
|
FINISHED |
| Object | female clone |
—
|
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: female clone | Statement: [X-23, relationshipToWolverine, female clone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToWolverine Context triple: [X-23, relationshipToWolverine, female clone]
-
A.
relationshipToHulk
Indicates the specific familial, social, or interpersonal connection an entity has with the Hulk.
-
B.
relationshipToMarvelUniverse
Indicates the nature or type of connection an entity has to the Marvel universe, such as affiliation, role, or relevance within that fictional setting.
-
C.
relationshipToVigilantes
Indicates the nature or type of connection an entity has with vigilantes, such as affiliation, opposition, support, or other relational stance.
-
D.
relationshipToWinston
Indicates the specific type of personal, social, or familial connection that one entity has with Winston.
-
E.
relationshipToJamesBond
Indicates the specific familial, romantic, professional, or social relationship that one entity has to James Bond.
- 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a00b8e0a5508190abc5c1e492bed12e |
completed | May 10, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_6a00b8327d048190850af317f60f0f8b |
completed | May 10, 2026, 4:54 p.m. |
| PDg | Predicate description generation | batch_6a00b8dfde3c81908c04ceccf67329db |
completed | May 10, 2026, 4:57 p.m. |
Created at: April 28, 2026, 10:23 a.m.