Triple
T10205153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convention de Washington |
E242173
|
entity |
| Predicate | entréeEnVigueurLe |
P7730
|
FINISHED |
| Object | 1975-07-01 |
—
|
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: 1975-07-01 | Statement: [Convention de Washington, entréeEnVigueurLe, 1975-07-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entréeEnVigueurLe Context triple: [Convention de Washington, entréeEnVigueurLe, 1975-07-01]
-
A.
activeFrom
chosen
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
-
B.
occupationBegan
Indicates the point in time when an entity started holding a particular occupation or job.
-
C.
isDebut
Indicates that something is the first formal appearance or introduction of an entity, such as a person, work, or performance, in a particular context or domain.
-
D.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
-
E.
availabilityStart
Indicates the date and time from which something becomes available or active.
- 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.