Triple
T30370223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEC Technical Reports |
E772526
|
entity |
| Predicate | mayAlsoBeAvailableIn |
P154561
|
FINISHED |
| Object | French |
—
|
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: French | Statement: [IEC Technical Reports, mayAlsoBeAvailableIn, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayAlsoBeAvailableIn Context triple: [IEC Technical Reports, mayAlsoBeAvailableIn, French]
-
A.
mayBeAvailableIn
chosen
Indicates that an entity has the potential to be obtainable, accessible, or present within a specified context, location, or medium.
-
B.
alsoAvailableInVersion
Indicates that the same item, feature, or content is offered in another specified version or edition.
-
C.
mayAlsoBeProvidedAs
Indicates that something can optionally be supplied or made available in an alternative form or manner in addition to its primary provision.
-
D.
availableInCountry
Indicates that something can be legally or practically obtained, accessed, or used within a specified country.
-
E.
availableAs
Indicates that one entity can be used, accessed, or offered in the form, role, or capacity of another entity.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682836d308190b22a0efc893e7a45 |
completed | May 2, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:59 p.m.