Triple
T29475085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | auteur theory |
E747627
|
entity |
| Predicate | associatedWithCritic |
P207152
|
FINISHED |
| Object | François Truffaut |
E94306
|
NE 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: François Truffaut | Statement: [auteur theory, associatedWithCritic, François Truffaut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCritic Context triple: [auteur theory, associatedWithCritic, François Truffaut]
-
A.
criticRole
Indicates that an entity serves in the capacity or function of a critic in relation to another entity or work.
-
B.
alsoCalledByCritics
Indicates that critics refer to the same entity by an alternative name or label.
-
C.
authorOfCriticalReception
Indicates that an entity is the author or creator of a critical review, evaluation, or reception of another work or subject.
-
D.
isCriticallyAssociatedWith
Indicates a strong, essential, and high-impact relationship between entities, where one significantly influences the success, function, or outcome of the other.
-
E.
usesCriticCount
Indicates that something bases its evaluation, decision, or outcome on the number of critics involved.
- F. None of above. chosen
Provenance (5 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26c8d121808190ada906d2384d145d |
completed | June 8, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 28, 2026, 3:59 p.m.