Triple
T6231393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Framework for Integrated Test |
E139361
|
entity |
| Predicate | supportsMethodology |
P11868
|
FINISHED |
| Object | agile software development |
—
|
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: agile software development | Statement: [Framework for Integrated Test, supportsMethodology, agile software development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMethodology Context triple: [Framework for Integrated Test, supportsMethodology, agile software development]
-
A.
hasMethodologyDocument
Indicates that an entity is associated with, or supported by, a specific methodology document that defines its procedures or approach.
-
B.
methodologyType
Indicates the specific kind or category of method or procedure used in carrying out an activity or study.
-
C.
describesMethodology
Indicates that one entity explains, specifies, or characterizes the methodology or procedure used by another entity.
-
D.
methodologicallyAssociatedWith
Indicates a relationship where two entities are connected through shared, related, or jointly applied methods, procedures, or methodological approaches.
-
E.
supportedParadigm
chosen
Indicates that one entity (such as a tool, language, or system) provides functionality or features that enable or are compatible with a particular paradigm or methodological approach.
- 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_69c008afd3148190b71e9eaa60420dd1 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062ec5be4819084d6df2e8dd2a542 |
completed | March 22, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69c05601de6481909d0880048fd7b49a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:22 p.m.