Triple
T31283582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parquet national antiterroriste |
E797739
|
entity |
| Predicate | usesProceduralLanguage |
P64764
|
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: [Parquet national antiterroriste, usesProceduralLanguage, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProceduralLanguage Context triple: [Parquet national antiterroriste, usesProceduralLanguage, French]
-
A.
usedProceduralLanguage
Indicates that an entity carried out an action or implemented something by means of a procedural programming language.
-
B.
procedureLanguage
chosen
Indicates the programming or formal language in which a given procedure, method, or algorithm is expressed or implemented.
-
C.
procedureLanguageChoice
Indicates that a specific programming or scripting language is selected or used to implement or define a given procedure.
-
D.
hasProceduralRole
Indicates that an entity participates in a process or procedure by fulfilling a specific functional role within that process.
-
E.
proceduresDefinedBy
Indicates that certain procedures are specified, established, or authored by a particular 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 29, 2026, 9:13 p.m.