Triple
T14857264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Aix-la-Chapelle (1748) |
E349390
|
entity |
| Predicate | requiredReturnOf |
P85956
|
FINISHED |
| Object | Louisbourg to Great Britain |
—
|
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: Louisbourg to Great Britain | Statement: [Treaty of Aix-la-Chapelle (1748), requiredReturnOf, Louisbourg to Great Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredReturnOf Context triple: [Treaty of Aix-la-Chapelle (1748), requiredReturnOf, Louisbourg to Great Britain]
-
A.
returnRequirement
chosen
Indicates that an entity is obligated or expected to be sent back or restored to its original source or owner.
-
B.
requiredToProvide
Indicates that one entity has an obligation or duty to supply or furnish something to another entity.
-
C.
returns
Indicates that one entity gives or sends something back to another entity, often as a result or outcome of a process or action.
-
D.
returnedBy
Indicates that something is given, sent, or brought back to a previous sender, owner, or source by another entity.
-
E.
returnsAs
Indicates that one entity goes back to or resumes a previous state, location, role, or condition associated with another entity.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded44458ec8190be295a95f5daab14 |
completed | April 14, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:54 a.m.