Triple
T17675548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Active Job |
E440633
|
entity |
| Predicate | jobDefinitionPattern |
P128511
|
FINISHED |
| Object | class MyJob < ActiveJob::Base |
—
|
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: class MyJob < ActiveJob::Base | Statement: [Active Job, jobDefinitionPattern, class MyJob < ActiveJob::Base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jobDefinitionPattern Context triple: [Active Job, jobDefinitionPattern, class MyJob < ActiveJob::Base]
-
A.
languagePattern
Indicates a recurring or structured way in which language is used, organized, or formed within a given context.
-
B.
flagPattern
Indicates that one entity has a flag whose design or pattern matches or represents the other entity.
-
C.
dstRulePattern
Indicates a rule-based pattern that specifies or constrains the characteristics of a destination in a relationship or process.
-
D.
fieldPattern
Indicates a recurring or structured arrangement or configuration present within a field or area.
-
E.
moduloPatternName
Indicates that an entity is associated with a specific naming pattern used for modulo-based grouping or partitioning.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6cca54819094ea0bed1517724e |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10 a.m.