Triple
T34170472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Transylvania |
E876529
|
entity |
| Predicate | returnProcess |
P187076
|
FINISHED |
| Object | Paris Peace Treaties |
—
|
NE NERFINISHED |
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: Paris Peace Treaties | Statement: [Northern Transylvania, returnProcess, Paris Peace Treaties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnProcess Context triple: [Northern Transylvania, returnProcess, Paris Peace Treaties]
-
A.
returnService
Indicates a relationship where a service that was previously provided is being sent back, reversed, or requested to be undone or refunded.
-
B.
returnProcession
Indicates a movement or sequence of entities traveling back to a prior location or state, typically as part of a formal or organized return.
-
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.
returnStatus
Indicates the current outcome or condition of a previously initiated return action or process.
-
E.
returnedWith
Indicates that an entity came back or was brought back accompanied by, or in possession of, another specified entity.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb3424724c8190ba55ecf66fa0b171 |
completed | May 6, 2026, 12:29 p.m. |
Created at: May 1, 2026, 1:54 a.m.