Triple
T13284949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netchaïev est de retour |
E316418
|
entity |
| Predicate | lié à |
P37
|
FINISHED |
| Object | tradition du roman politique européen du XXe siècle |
—
|
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: tradition du roman politique européen du XXe siècle | Statement: [Netchaïev est de retour, lié à, tradition du roman politique européen du XXe siècle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lié à Context triple: [Netchaïev est de retour, lié à, tradition du roman politique européen du XXe siècle]
-
A.
moreCloselyRelatedTo
Indicates that one entity has a stronger or closer relationship, connection, or similarity to a second entity than to some other reference entity.
-
B.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
C.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
D.
ligadoA
Indicates that one entity is connected, linked, or otherwise associated with another entity.
-
E.
relatedField
Indicates that one field, topic, or area of study is connected or relevant to another in subject matter or application.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:27 p.m.