Triple
T4575400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supplementary Private Use Area-B |
E123129
|
entity |
| Predicate | containsAssignedCharacters |
P58050
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Supplementary Private Use Area-B, containsAssignedCharacters, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsAssignedCharacters Context triple: [Supplementary Private Use Area-B, containsAssignedCharacters, false]
-
A.
containsCharacter
Indicates that one entity includes a specific character as part of its content or composition.
-
B.
associatedWithCharacterGroup
Indicates that an entity has a connection or affiliation with a particular group of characters.
-
C.
usesCharactersAs
Indicates that one entity employs or incorporates specific characters (such as letters, symbols, or glyphs) from another entity for its representation or functioning.
-
D.
hasSpecialCharacter
Indicates that a given entity (such as a string or identifier) contains at least one non-alphanumeric special character.
-
E.
hasParentCharacter
Indicates that one character is the parent of another character.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c9f0bc81908d87f01ab067818a |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:10 p.m.