Triple
T2169682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikolaj Bjørner |
E46992
|
entity |
| Predicate | toolDeveloperFor |
P37347
|
FINISHED |
| Object | SMT-based verification tools |
—
|
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: SMT-based verification tools | Statement: [Nikolaj Bjørner, toolDeveloperFor, SMT-based verification tools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toolDeveloperFor Context triple: [Nikolaj Bjørner, toolDeveloperFor, SMT-based verification tools]
-
A.
toolIn
Indicates that one entity is a tool or instrument used in or associated with another entity or context.
-
B.
toolUsed
Indicates that an action or task is performed using a particular tool as the means or instrument.
-
C.
coPilotWith
Indicates that two entities jointly serve as pilots or share piloting responsibilities for the same vehicle or mission.
-
D.
toolUseExamples
Indicates that one entity provides example instances or demonstrations of how a particular tool is or can be used by another entity.
-
E.
developmentFunction
Indicates a relationship where one entity serves as a function, role, or mechanism that drives, supports, or shapes the development or growth of another entity.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc1559ff481908efe3f214b2570dc |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbd9efc1c81909a65044a1ffc9038 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abc153b22481908115e5f582c93f12 |
completed | March 7, 2026, 6:10 a.m. |
Created at: March 4, 2026, 7:45 p.m.