Triple
T5652859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Two Little Girls in Blue |
E124545
|
entity |
| Predicate | featuresTelepathy |
P65440
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Two Little Girls in Blue, featuresTelepathy, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresTelepathy Context triple: [Two Little Girls in Blue, featuresTelepathy, true]
-
A.
featuresSuit
Indicates that one entity includes or presents a particular suit (e.g., clothing, armor, or outfit) as a notable component or attribute.
-
B.
technologicalFeature
Indicates that one entity possesses, exhibits, or is characterized by a specific technological capability, component, or functionality in relation to another entity.
-
C.
featuresText
Indicates that an entity includes or presents a specific piece of text as one of its characteristics or contents.
-
D.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
E.
connectivityFeatures
Indicates the types of network or communication options that are available or supported for connecting to or through an entity.
- 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022d8a2588190b10de59edbc8841f |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2274b48190b2ef57ed728f785c |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0727bc8190b16e9a669c04b4dd |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:42 p.m.