Triple
T25706948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enid Blyton Adventure Series |
E644617
|
entity |
| Predicate | featuresGroupType |
P17143
|
FINISHED |
| Object | group of children |
—
|
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: group of children | Statement: [Enid Blyton Adventure Series, featuresGroupType, group of children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresGroupType Context triple: [Enid Blyton Adventure Series, featuresGroupType, group of children]
-
A.
featuresGroup
chosen
Indicates that an entity includes or is associated with a specific group as one of its features or components.
-
B.
featureTypeCatalog
Indicates that an entity is associated with, or defined by, a catalog that specifies the types of features it can include or reference.
-
C.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
D.
featureSet
Indicates that one entity is a collection or configuration of features associated with or applied to another entity.
-
E.
featuresSegment
Indicates that one entity includes or highlights a particular segment or portion of another entity as a notable part of it.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 21, 2026, 9:05 p.m.