Triple
T4443196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Base |
E96218
|
entity |
| Predicate | loadedByDefaultIn |
P49353
|
FINISHED |
| Object | Julia session |
—
|
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: Julia session | Statement: [Base, loadedByDefaultIn, Julia session]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loadedByDefaultIn Context triple: [Base, loadedByDefaultIn, Julia session]
-
A.
appliesByDefaultWhen
chosen
Indicates that one condition, rule, or behavior is automatically in effect whenever a specified situation or context occurs, without requiring explicit activation.
-
B.
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.
-
C.
disabledByDefaultIn
Indicates that a feature, capability, or setting is turned off by default within the specified context or environment.
-
D.
runsByDefault
Indicates that an action, process, or behavior is executed automatically without requiring explicit configuration or invocation.
-
E.
builtIn
Indicates that one entity is inherently included as a standard, pre-existing component or feature of another entity, rather than being added or installed separately.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355aef21c819088f168a23f1933a6 |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.