Triple
T33809878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcus Rowland |
E866498
|
entity |
| Predicate | hasBibliographyOn |
P45309
|
FINISHED |
| Object | RPGGeek |
—
|
NE NERFINISHED |
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: RPGGeek | Statement: [Marcus Rowland, hasBibliographyOn, RPGGeek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBibliographyOn Context triple: [Marcus Rowland, hasBibliographyOn, RPGGeek]
-
A.
hasBibliography
chosen
Indicates that one entity includes or is associated with a bibliography listing referenced or related works.
-
B.
hasBibliographySize
Indicates the relationship between a work and the size or length of its bibliography, typically expressed as a count of referenced items.
-
C.
hasGenreInBibliography
Indicates that a work’s bibliography includes sources belonging to a specified genre.
-
D.
bibliographicContribution
Indicates that an entity has contributed to the creation, authorship, or production of a bibliographic resource (such as a book, article, or other documented work).
-
E.
followsInBibliography
Indicates that one bibliographic entry directly succeeds another in the ordering of a bibliography or reference list.
- 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_69f3499057fc81909d862b1309a3bd71 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 1:46 a.m.