Triple
T6993330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proximal Policy Optimization |
E162136
|
entity |
| Predicate | arXivId |
P31984
|
FINISHED |
| Object | 1707.06347 |
—
|
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: 1707.06347 | Statement: [Proximal Policy Optimization, arXivId, 1707.06347]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arXivId Context triple: [Proximal Policy Optimization, arXivId, 1707.06347]
-
A.
arxivId
chosen
Indicates that an entity (such as a paper or work) is associated with a specific arXiv identifier used to reference it in the arXiv repository.
-
B.
relatedIdentifier
Indicates that one identifier is associated with another identifier that refers to the same or a related entity in a different context or system.
-
C.
citationSystem
Indicates a relationship where one entity specifies or uses a particular system, style, or standard for formatting and managing citations.
-
D.
citationKey
Indicates a unique identifier assigned to a specific citation or bibliographic reference within a collection of references.
-
E.
isResearchHub
Indicates that an entity serves as a central location or focal point for conducting, coordinating, or supporting research activities.
- 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbc30fdc81909244d83c8178755c |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:32 p.m.