Triple
T248645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proceedings of the Royal Society |
E5092
|
entity |
| Predicate | seriesSubdivision |
P1761
|
FINISHED |
| Object | Series A |
—
|
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: Series A | Statement: [Proceedings of the Royal Society, seriesSubdivision, Series A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesSubdivision Context triple: [Proceedings of the Royal Society, seriesSubdivision, Series A]
-
A.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
B.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
-
C.
divisionTitles
Indicates that an entity holds or is associated with one or more titles or championships within a specific division or category.
-
D.
subdivisionRank
Indicates the hierarchical level or type of administrative or territorial subdivision that an entity occupies within a larger organizational or geographic structure.
-
E.
isSeriesOf
chosen
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d35aa288190966b6e15af1525cb |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b64ea3081908de626a0e1445bdb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.