Triple
T27736103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ParameterizedThreadStart |
E697531
|
entity |
| Predicate | threadStartPattern |
P87534
|
FINISHED |
| Object | parameterized thread entry point |
—
|
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: parameterized thread entry point | Statement: [ParameterizedThreadStart, threadStartPattern, parameterized thread entry point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threadStartPattern Context triple: [ParameterizedThreadStart, threadStartPattern, parameterized thread entry point]
-
A.
hasStartPattern
chosen
Indicates that something begins with, or is characterized at its outset by, a specified pattern.
-
B.
processStartsWith
Indicates that a process begins with, or is initially triggered by, a specified preceding event, state, or action.
-
C.
flagPattern
Indicates that one entity has a flag whose design or pattern matches or represents the other entity.
-
D.
namePattern
Indicates that an entity’s name follows or matches a specified pattern or format.
-
E.
maskPattern
Indicates a relationship where one entity serves as a masking template or pattern that determines which parts or aspects of another entity are revealed, hidden, or transformed.
- 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_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 3:12 p.m.