Triple
T10148551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le festin de l’araignée |
E231768
|
entity |
| Predicate | isProgrammatic |
P92508
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Le festin de l’araignée, isProgrammatic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProgrammatic Context triple: [Le festin de l’araignée, isProgrammatic, true]
-
A.
programmatic
Indicates that one entity is created, controlled, or executed through code or automated software instructions rather than through manual or interactive means.
-
B.
programmedVia
Indicates that one entity is created, configured, or made to operate through the use of another entity as its programming method, tool, or medium.
-
C.
hasProgramCode
Indicates that an entity is associated with a specific program identifier or code used to reference or classify it within a system.
-
D.
implementedProgram
Indicates that an entity has created, developed, or put into operation a particular program or software system.
-
E.
implementsProgram
Indicates that an entity carries out, executes, or puts into effect a specified program or plan.
- F. None of above. chosen
Provenance (4 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_69ca848364f881908a24366a6feec1db |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec024da481908b8170fcf3b18e67 |
completed | April 2, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba4f5d88190ba68e63be10b08c7 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd51bc440c819086320900701f87c2 |
completed | April 1, 2026, 5:11 p.m. |
Created at: March 30, 2026, 9:08 p.m.