Triple
T33900911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malthopsis |
E869043
|
entity |
| Predicate | finModificationFunction |
P6654
|
FINISHED |
| Object | support on substrate |
—
|
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: support on substrate | Statement: [Malthopsis, finModificationFunction, support on substrate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finModificationFunction Context triple: [Malthopsis, finModificationFunction, support on substrate]
-
A.
modificationBy
Indicates that one entity has been altered, changed, or adjusted as a result of an action performed by another entity.
-
B.
functionChange
chosen
Indicates that an entity’s function, role, or operational behavior has been altered from one state or purpose to another.
-
C.
finVariation
Indicates a relationship where one entity represents a variation, version, or modified form of another.
-
D.
modification
Indicates a change made to an existing entity, altering its properties, structure, or state from a prior version.
-
E.
modificationProgram
Indicates that an entity is subject to, or associated with, a program or process that alters, updates, or changes its properties or state.
- 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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.