Triple
T35685681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Kukus |
E1031138
|
entity |
| Predicate | hasFormExperimentation |
P194317
|
FINISHED |
| Object | nonlinear structure |
—
|
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: nonlinear structure | Statement: [High Kukus, hasFormExperimentation, nonlinear structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormExperimentation Context triple: [High Kukus, hasFormExperimentation, nonlinear structure]
-
A.
hasFormatExperimentation
chosen
Indicates that an entity is involved in testing or varying different formats or structures to evaluate their effectiveness or impact.
-
B.
includesExperiment
Indicates that one entity contains or encompasses a specific experiment as part of its scope, composition, or content.
-
C.
hasTypeOfExperiment
Indicates that an experiment is associated with or classified under a specific type or category of experiment.
-
D.
supportsExperiment
Indicates that one entity provides the necessary resources, conditions, or assistance for an experiment to be conducted or to function as intended.
-
E.
featuresExperiment
Indicates that an entity is involved in, or is the subject of, a specific experimental setup, test, or trial.
- 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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.