Triple
T20889181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book IX: The Merchants |
E514363
|
entity |
| Predicate | writtenAsPartOf |
P112672
|
FINISHED |
| Object | missionary ethnography |
—
|
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: missionary ethnography | Statement: [Book IX: The Merchants, writtenAsPartOf, missionary ethnography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenAsPartOf Context triple: [Book IX: The Merchants, writtenAsPartOf, missionary ethnography]
-
A.
writtenPartIncludes
chosen
Indicates that a written work or document contains another written segment as one of its constituent parts.
-
B.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
C.
writtenByParticipantIn
Indicates that something (such as a document, message, or content) was authored by an entity that is a participant in a specified event, process, or context.
-
D.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
-
E.
willWrittenIn
Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d05be4a081908de0d3f5dbe4429a |
completed | April 21, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.