Triple
T248652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proceedings of the Royal Society |
E5092
|
entity |
| Predicate | editorialStandard |
P8779
|
FINISHED |
| Object | international |
—
|
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: international | Statement: [Proceedings of the Royal Society, editorialStandard, international]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editorialStandard Context triple: [Proceedings of the Royal Society, editorialStandard, international]
-
A.
editorialProcess
Indicates the process by which content is reviewed, revised, and approved before publication or release.
-
B.
editedBy
Indicates that one entity has revised, modified, or otherwise made editorial changes to another entity.
-
C.
hasEditorialFocus
Indicates that an entity (such as a publication or section) is primarily concerned with or oriented around a particular editorial topic, theme, or subject area.
-
D.
edition
Indicates that one entity is a specific version, issue, or release of another (typically a work such as a book, journal, or software).
-
E.
hasEditorialBoard
Indicates that an entity (such as a publication or journal) is overseen or governed by a specific editorial board.
- 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_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. |
| PDg | Predicate description generation | batch_69a25c2ca46c81908c61696f31e59a98 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.