Triple
T35674967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emmalee |
E1030831
|
entity |
| Predicate | hasNameFormationType |
P75423
|
FINISHED |
| Object | creative respelling |
—
|
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: creative respelling | Statement: [Emmalee, hasNameFormationType, creative respelling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameFormationType Context triple: [Emmalee, hasNameFormationType, creative respelling]
-
A.
usesNameForm
Indicates that one entity adopts or applies a particular standardized form or variant of a name associated with another entity.
-
B.
isGivenNameFormOf
Indicates that one name is a given-name variant or form derived from another name.
-
C.
hasWordFormation
chosen
Indicates that one linguistic unit is formed or derived from another through a specific word-formation process (such as compounding, derivation, or affixation).
-
D.
hasHumanFormName
Indicates that an entity’s human form is known by a specific name.
-
E.
appliesToFormationName
Indicates that something (such as a rule, property, or classification) is relevant or applicable specifically to a named geological or structural formation.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:05 p.m.