Triple
T32214979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isabelle/FOL |
E822902
|
entity |
| Predicate | loadedVia |
P145038
|
FINISHED |
| Object | theory import in Isabelle |
—
|
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: theory import in Isabelle | Statement: [Isabelle/FOL, loadedVia, theory import in Isabelle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loadedVia Context triple: [Isabelle/FOL, loadedVia, theory import in Isabelle]
-
A.
loadedWith
Indicates that one entity is carrying, filled with, or heavily supplied with another entity.
-
B.
loader
chosen
Indicates a relationship where an entity is responsible for loading or placing items, data, or resources into another system, container, or context.
-
C.
launchedVia
Indicates that an entity is initiated, deployed, or started by means of a specified method, mechanism, or intermediary.
-
D.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
E.
canBeLoadedAt
Indicates that an entity is capable of being placed onto or into another entity (such as a vehicle, container, or system) at a specific location or point in time.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb95ffc48190bb4a7319a05834d6 |
completed | May 3, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:37 a.m.