Triple
T29984029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Curiosities of a Hothouse |
E761677
|
entity |
| Predicate | hasCreatorName |
P41370
|
FINISHED |
| Object | Christopher Reid |
—
|
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: Christopher Reid | Statement: [The Curiosities of a Hothouse, hasCreatorName, Christopher Reid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCreatorName Context triple: [The Curiosities of a Hothouse, hasCreatorName, Christopher Reid]
-
A.
creatorGivenName
Indicates the given (first) name of the person or entity that created something.
-
B.
authorRealNameOfCreator
Indicates that a person’s real, legal, or birth name is the true identity behind a creator who may be known by a pseudonym or handle.
-
C.
creatorFullName
chosen
Indicates the full personal name of the entity that created or authored another entity.
-
D.
hasPrimaryCreators
Indicates that the related entities are the main or principal creators responsible for originating or producing something.
-
E.
creatorNameInOriginalScript
Indicates that the relationship specifies the name of the creator written in the original script or writing system used by that creator.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 29, 2026, 6:36 p.m.