Triple
T27926596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apress Pro series |
E707852
|
entity |
| Predicate | editorialLevel |
P164545
|
FINISHED |
| Object | advanced |
—
|
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: advanced | Statement: [Apress Pro series, editorialLevel, advanced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editorialLevel Context triple: [Apress Pro series, editorialLevel, advanced]
-
A.
editorialStandard
Indicates that one entity defines, follows, or enforces a particular set of editorial rules, guidelines, or quality criteria in relation to another entity or content.
-
B.
editorialRole
Indicates that one entity holds an editorial position or responsibility in relation to another entity, such as a publication, work, or organization.
-
C.
editorialControl
Indicates that one entity has the authority to direct, modify, or approve the content or presentation produced by another entity.
-
D.
editorialLine
Indicates the overarching editorial stance, policy, or perspective that guides how content is selected, framed, and presented.
-
E.
editorialFunction
Indicates that one entity performs an editorial role or responsibility in relation to another entity, such as overseeing, revising, or curating its content.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 7 p.m.