Triple
T29002656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Red-Haired Girl |
E736344
|
entity |
| Predicate | canonicalNameInStrip |
P105242
|
FINISHED |
| Object | not explicitly given |
—
|
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: not explicitly given | Statement: [Little Red-Haired Girl, canonicalNameInStrip, not explicitly given]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalNameInStrip Context triple: [Little Red-Haired Girl, canonicalNameInStrip, not explicitly given]
-
A.
hasCanonicalNameForm
Indicates that an entity is associated with its standard or officially recognized name form.
-
B.
lessCommonNameFor
Indicates that the subject is a less commonly used name or label for the same entity or concept as the object.
-
C.
commonNameOf
Indicates that one entity is the commonly used or popular name by which the other entity is known.
-
D.
exportName
Indicates that one entity is exported under a specific name or label in relation to another context or system.
-
E.
canonicallyReferredToAs
chosen
Indicates that one entity is the officially recognized or standard name or label by which another entity is known.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fbd59d0819095a6bfb40c7c96d5 |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:35 a.m.