Triple
T10158711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CTCP |
E233833
|
entity |
| Predicate | delimitedBy |
P38006
|
FINISHED |
| Object | ASCII 0x01 characters |
—
|
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: ASCII 0x01 characters | Statement: [CTCP, delimitedBy, ASCII 0x01 characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: delimitedBy Context triple: [CTCP, delimitedBy, ASCII 0x01 characters]
-
A.
separatesBy
Indicates that one entity divides, partitions, or creates a boundary between two or more other entities.
-
B.
alternativeDelimiters
Indicates a relationship where one or more substitute boundary markers are used in place of the primary delimiters for separating or enclosing elements.
-
C.
blockDelimiter
chosen
Indicates that one entity serves as a boundary marker that starts, ends, or separates a logical block associated with another entity.
-
D.
separatedFromSerialBy
Indicates that one entity is positioned with a serial element (such as a serial number or serial identifier) acting as a separator between it and another entity.
-
E.
separatesAt
Indicates that one entity divides or splits another entity into distinct parts at a specific point, boundary, or location.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec56d944819081bc6ea36c905ba2 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:09 p.m.