Triple
T34668751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Snake |
E890322
|
entity |
| Predicate | cloneProject |
P179598
|
FINISHED |
| Object | Les Enfants Terribles |
—
|
NE NERFINISHED |
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: Les Enfants Terribles | Statement: [Old Snake, cloneProject, Les Enfants Terribles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cloneProject Context triple: [Old Snake, cloneProject, Les Enfants Terribles]
-
A.
exportProject
Indicates initiating the transfer or packaging of a project’s data or configuration from one system, format, or environment to another.
-
B.
cloneCommander
Indicates that one entity serves as the commanding officer or leader of a clone (or group of clones), holding authority and responsibility over them.
-
C.
cloneLine
Indicates that one line is a duplicate or exact copy of another line.
-
D.
parentProject
Indicates that one project serves as the direct higher-level or containing project in relation to another project.
-
E.
isSisterProjectOf
Indicates that two projects are related and aligned in purpose or scope, typically operating in parallel under a common umbrella or organization.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722f904b0819091ffa4ea4621e8b4 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: May 1, 2026, 2:05 a.m.