Triple
T37658398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DbTransaction |
E937655
|
entity |
| Predicate | hasDerivedClass |
P176185
|
FINISHED |
| Object | SqlTransaction |
—
|
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: SqlTransaction | Statement: [DbTransaction, hasDerivedClass, SqlTransaction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDerivedClass Context triple: [DbTransaction, hasDerivedClass, SqlTransaction]
-
A.
isDerivedFromGivenName
Indicates that one entity originates from, or is formed based on, a specified given (first) name.
-
B.
isSuperclassOf
chosen
Indicates that one class is a more general class from which another class directly or indirectly inherits.
-
C.
usesSubclass
Indicates that one entity makes use of, depends on, or operates through a more specific subclass of another entity.
-
D.
hasPrototype
Indicates that an entity is based on, derived from, or exemplified by a specific prototype.
-
E.
derivedFrom
Indicates that one entity originates, is obtained, or is developed from another source 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffada24d188190a576a02dc280a7fb |
completed | May 9, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69ffad46d6ac819081772f408b1389d5 |
completed | May 9, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:18 p.m.