Triple
T27736060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ThreadStart |
E697530
|
entity |
| Predicate | threadEntryPoint |
P44371
|
FINISHED |
| Object | method executed when Thread.Start is called |
—
|
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: method executed when Thread.Start is called | Statement: [ThreadStart, threadEntryPoint, method executed when Thread.Start is called]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threadEntryPoint Context triple: [ThreadStart, threadEntryPoint, method executed when Thread.Start is called]
-
A.
entryPointFor
Indicates that one entity serves as the access or starting location through which another entity is entered, initiated, or reached.
-
B.
programEntryMethod
chosen
Indicates that a method serves as the starting point or main entry method for executing a program or component.
-
C.
mainEntranceOn
Indicates that the primary entrance of one entity is located on or faces toward another entity, such as a particular side, street, or boundary.
-
D.
mainStartingPoint
Indicates the primary location or position from which an event, process, or path begins.
-
E.
mainEntranceLocation
Indicates the location where the primary or main entrance of an entity is situated.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 3:12 p.m.