Triple
T23235049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verma module |
E581261
|
entity |
| Predicate | hasSubmoduleStructureDescribedBy |
P151478
|
FINISHED |
| Object | root system |
—
|
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: root system | Statement: [Verma module, hasSubmoduleStructureDescribedBy, root system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubmoduleStructureDescribedBy Context triple: [Verma module, hasSubmoduleStructureDescribedBy, root system]
-
A.
includesSubmodule
Indicates that one module contains another module as a subordinate or component part within its structure.
-
B.
hasSubproject
Indicates that a project includes another project as a subordinate or component part within its overall structure.
-
C.
hasSubcomponent
Indicates that one entity is a constituent part or component of another, larger entity.
-
D.
hasSubConcept
Indicates that one concept is a more specific, subordinate, or narrower idea within the scope of another, more general concept.
-
E.
hasSubconfiguration
Indicates that an entity includes another entity as a subordinate or component configuration within its overall structure.
- 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192e8c7548190b53434eeb2620a6e |
completed | April 29, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:09 p.m.