Triple
T10205151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convention de Washington |
E242173
|
entity |
| Predicate | adoptéeLe |
P36255
|
FINISHED |
| Object | 1973-03-03 |
—
|
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: 1973-03-03 | Statement: [Convention de Washington, adoptéeLe, 1973-03-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptéeLe Context triple: [Convention de Washington, adoptéeLe, 1973-03-03]
-
A.
adopted
Indicates that one entity has legally taken another (often a child or animal) into its family or care as a permanent member.
-
B.
adoptadoEl
Indicates that one entity has been adopted by another entity (e.g., a person, family, or organization).
-
C.
adoptedPursuantTo
Indicates that something (such as a measure, policy, or decision) was formally adopted in accordance with, and on the basis of, a specific legal authority, procedure, or instrument.
-
D.
adoptedBy
Indicates that an entity has been taken in and legally or formally accepted as a child, member, or responsibility by another entity.
-
E.
officiallyAdopted
chosen
Indicates that an entity has been formally accepted, approved, or enacted by an authorized body or process as the recognized standard or version.
- 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_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. |
Created at: April 6, 2026, 10:42 a.m.