Triple
T35073204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Translating Mo’um |
E1011937
|
entity |
| Predicate | workInAuthorCorpusOrder |
P182076
|
FINISHED |
| Object | early collection |
—
|
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: early collection | Statement: [Translating Mo’um, workInAuthorCorpusOrder, early collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workInAuthorCorpusOrder Context triple: [Translating Mo’um, workInAuthorCorpusOrder, early collection]
-
A.
workOfAuthorOf
Indicates that one entity is a work (such as a book, article, or artwork) created by the author associated with another entity.
-
B.
appearsInWorkByAuthorFrom
Indicates that an entity appears in a work that was created by an author originating from a specified place or country.
-
C.
workBySameAuthorAs
Indicates that two works share the same author, i.e., they were created by the same person or entity.
-
D.
workOfAuthorWho
Indicates that one entity is a work (such as a book, article, or artwork) created by another entity who is its author.
-
E.
authorOrder
Indicates the sequence or ranking of authors associated with a work, specifying each author's position in the authorship list.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78658f6fc8190ba08ce880a6568e5 |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.