Triple
T26966059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDD |
E679174
|
entity |
| Predicate | strategicDesignConcept |
P134579
|
FINISHED |
| Object | core domain |
—
|
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: core domain | Statement: [DDD, strategicDesignConcept, core domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicDesignConcept Context triple: [DDD, strategicDesignConcept, core domain]
-
A.
conceptualStrategy
chosen
Indicates a relationship where an entity employs or is associated with an abstract, high-level plan or approach for achieving a goal or solving a problem.
-
B.
tacticalDesignConcept
Indicates a conceptual plan or approach that defines how tactical actions or operations should be structured and executed.
-
C.
creativeStrategy
Indicates a relationship where an entity develops or employs an overarching creative plan or approach to guide how ideas are expressed or executed.
-
D.
designPhilosophy
Indicates the guiding principles, values, or conceptual approach that shape how something is designed or created.
-
E.
overallDesignGoal
Indicates that one entity specifies or represents the primary design objective or guiding design intent for another entity.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 6:35 a.m.