Triple
T38422633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I, Robot (short story) |
E903272
|
entity |
| Predicate | authorCollectivePseudonymFor |
P197314
|
FINISHED |
| Object | Earl Binder |
—
|
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: Earl Binder | Statement: [I, Robot (short story), authorCollectivePseudonymFor, Earl Binder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorCollectivePseudonymFor Context triple: [I, Robot (short story), authorCollectivePseudonymFor, Earl Binder]
-
A.
authorCollective
Indicates that a work is created or authored by a collective group rather than by an individual.
-
B.
pseudonymCoinedBy
Indicates that a particular pseudonym was created or invented by a specific agent or source.
-
C.
coAppearsWithPseudonym
Indicates that an entity appears together with another entity that is identified or referenced by a pseudonym in the same context or source.
-
D.
authorOfNamesFor
Indicates that one entity is the creator or originator of the names assigned to another entity or set of entities.
-
E.
pseudonymOfArtist
Indicates that one name is a pseudonym used by an artist as an alternative to their real or primary name.
- 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_69f76e67e4fc8190a7d08dfe9a8af998 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
| PDg | Predicate description generation | batch_69fe86c98d688190a99d5dcb14e2dc95 |
completed | May 9, 2026, 12:58 a.m. |
Created at: May 3, 2026, 4:31 p.m.