Triple
T31792956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SRP |
E811518
|
entity |
| Predicate | isFirstPrincipleOf |
P66597
|
FINISHED |
| Object | SOLID |
—
|
NE NERFINISHED |
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: SOLID | Statement: [SRP, isFirstPrincipleOf, SOLID]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFirstPrincipleOf Context triple: [SRP, isFirstPrincipleOf, SOLID]
-
A.
principle1
chosen
Indicates that one entity serves as a primary rule, guideline, or foundational principle governing or guiding another entity.
-
B.
principle11
Indicates that an entity is governed or characterized by the eleventh principle within a defined ordered set of principles.
-
C.
hasFoundingPrinciple
Indicates that one entity serves as the core founding principle or fundamental guiding tenet upon which another entity is established or based.
-
D.
involvesPrinciple
Indicates that an action, process, or situation is based on, governed by, or makes essential use of a particular principle.
-
E.
principleClarified
Indicates that a principle has been made clearer or more explicit, typically by explanation, refinement, or elaboration.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ac1b460481909fd5c89485645533 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:39 p.m.