Triple
T6441967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCS |
E138245
|
entity |
| Predicate | characterModel |
P68217
|
FINISHED |
| Object | abstract characters with numeric code points |
—
|
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: abstract characters with numeric code points | Statement: [UCS, characterModel, abstract characters with numeric code points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterModel Context triple: [UCS, characterModel, abstract characters with numeric code points]
-
A.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
-
B.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
C.
modeledBy
chosen
Indicates that one entity serves as a model or representation of another, typically capturing its structure, behavior, or properties.
-
D.
characterDesigner
Indicates a relationship where an entity is responsible for designing or creating the visual or conceptual characteristics of a character.
-
E.
characterBasedOn
Indicates that one character is modeled, inspired, or derived from another real or fictional entity.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06989dfb88190b25ff8b2c53f3ced |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:46 p.m.