Triple
T34474652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Institut du Monde Arabe |
E884997
|
entity |
| Predicate | foundedByTreatyBetween |
P99458
|
FINISHED |
| Object | France |
—
|
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: France | Statement: [Institut du Monde Arabe, foundedByTreatyBetween, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedByTreatyBetween Context triple: [Institut du Monde Arabe, foundedByTreatyBetween, France]
-
A.
treatyConcludedBy
Indicates that a treaty was formally agreed upon, finalized, or brought into effect by a specified party or parties.
-
B.
treatyOf
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
-
C.
treatySignedWith
Indicates that a formal treaty or agreement has been officially signed between two parties.
-
D.
treatySignedFor
Indicates that a formal treaty has been signed on behalf of, or in representation of, a particular entity, cause, or subject.
-
E.
establishedByTreatyOrAct
chosen
Indicates that the relationship or entity was formally created, defined, or authorized through a specific treaty or legislative act.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: May 1, 2026, 2:01 a.m.