Triple
T1919973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISSN International Centre |
E40102
|
entity |
| Predicate | hasNetworkSize |
P33160
|
FINISHED |
| Object | more than 90 national and regional ISSN centres |
—
|
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: more than 90 national and regional ISSN centres | Statement: [ISSN International Centre, hasNetworkSize, more than 90 national and regional ISSN centres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNetworkSize Context triple: [ISSN International Centre, hasNetworkSize, more than 90 national and regional ISSN centres]
-
A.
hasBoardSize
Indicates that an entity is associated with a board whose dimensions or overall size are specified.
-
B.
stateSize
Indicates the relative or absolute physical extent or dimensions of a state, such as its area or population size.
-
C.
hasMinimumSize
Indicates that an entity meets or exceeds a specified minimum size threshold.
-
D.
networkLength
Indicates the total measured extent or distance covered by a network (e.g., of connections, links, or paths).
-
E.
hasAudienceSize
Indicates the relationship between an entity and the number of people or size of group that receives, views, or engages with it.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb213af0481909429ec971860a3fd |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb1b180e481908bbe893d6ba6208b |
completed | March 7, 2026, 5:03 a.m. |
Created at: March 4, 2026, 7:35 p.m.