Triple
T13015806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maffeo Polo |
E322547
|
entity |
| Predicate | roleAtMongolCourt |
P107839
|
FINISHED |
| Object | envoy |
—
|
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: envoy | Statement: [Maffeo Polo, roleAtMongolCourt, envoy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtMongolCourt Context triple: [Maffeo Polo, roleAtMongolCourt, envoy]
-
A.
roleInMonarchyPeriod
Indicates that an entity held a specific role or position during a defined period of a monarchy.
-
B.
emperorRole
Indicates that an entity holds or fulfills the role, position, or office of an emperor in relation to another entity or context.
-
C.
roleDuringCrusades
Indicates the specific function, position, or involvement an entity had in relation to the Crusades during the period they occurred.
-
D.
roleInAkbarsLife
Indicates the specific role, position, or significance that one entity held in relation to Akbar’s life.
-
E.
roleInManchuria
Indicates that an entity holds or held a specific role, position, or function in the context of Manchuria.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ecd04748190ade2530ee5db35fe |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e74283c819082e69ac3554fa7d8 |
completed | April 10, 2026, 10:49 p.m. |
Created at: April 9, 2026, 8:50 p.m.