Triple
T20889193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book IX: The Merchants |
E514363
|
entity |
| Predicate | aimedToDocument |
P4310
|
FINISHED |
| Object | indigenous customs |
—
|
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: indigenous customs | Statement: [Book IX: The Merchants, aimedToDocument, indigenous customs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimedToDocument Context triple: [Book IX: The Merchants, aimedToDocument, indigenous customs]
-
A.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
B.
aimedAtBy
Indicates that one entity serves as the target or goal toward which another entity directs an action, intention, or focus.
-
C.
aimedToFacilitate
Indicates an action or arrangement that was intentionally designed to make another process, event, or outcome easier or more likely to occur.
-
D.
documentedBy
chosen
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
E.
aimedToGrant
Indicates an intention or effort to provide or confer something (such as a right, benefit, or permission) to a recipient.
- 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.