Triple
T10205176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convention de Washington |
E242173
|
entity |
| Predicate | cible |
P92707
|
FINISHED |
| Object | États souverains |
—
|
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: États souverains | Statement: [Convention de Washington, cible, États souverains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cible Context triple: [Convention de Washington, cible, États souverains]
-
A.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
B.
reversible
Indicates that the relationship or process can proceed in both directions, allowing a return to the original state or configuration.
-
C.
controlled
Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state of another entity.
-
D.
transferable
Indicates that a right, property, or obligation can be legally or practically passed from one entity to another.
-
E.
tunable
Indicates that the associated entity can be adjusted or configured to different settings or values, typically to optimize performance or behavior.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa22071c819095febd18dd607978 |
completed | April 6, 2026, 12:42 p.m. |
| PD | Predicate disambiguation | batch_69d39559e5ac8190b88eca75956b7e6a |
completed | April 6, 2026, 11:13 a.m. |
| PDg | Predicate description generation | batch_69d3aa208c248190a0fb186b106389f3 |
completed | April 6, 2026, 12:42 p.m. |
Created at: April 6, 2026, 10:42 a.m.