Triple
T312787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Standard Serial Number |
E7642
|
entity |
| Predicate | hasSeparator |
P11855
|
FINISHED |
| Object | hyphen between fourth and fifth digit |
—
|
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: hyphen between fourth and fifth digit | Statement: [International Standard Serial Number, hasSeparator, hyphen between fourth and fifth digit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeparator Context triple: [International Standard Serial Number, hasSeparator, hyphen between fourth and fifth digit]
-
A.
hasMultipleSegments
Indicates that the referenced entity is composed of more than one distinct segment or section.
-
B.
hasSegmentType
Indicates that an entity is associated with, or classified by, a particular type or category of segment within a larger structure or sequence.
-
C.
hasPattern
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
D.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
E.
separates
Indicates that one entity divides, parts, or keeps other entities apart from each other.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea4aa16881909b2c8404b85992df |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e9428098819089d5950cd2c96dc4 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea08878c8190a5e8a90f620a3888 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.